Uh oh!
There was an error while loading. Please reload this page.
Conversation
treeowl
commented
Oct 3, 2018
If we add this, it definitely should be in its own module! |
chessai
commented
Oct 3, 2018
Oh yeah, that was another question I had, but forgot to ask in the first comment. I think I agree. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
| tell w = lift (tell w) | ||
| {-# INLINE tell #-} | ||
| --listen :: ListT m a -> ListT m (a, w) |
There was a problem hiding this comment.
I just mean it's not obvious to me what listen has to do in a stream contact and why this is how it's done. I'd appreciate a comment.
There was a problem hiding this comment.
Initially I thought that MonadWriter might be useful to build up a ListT, and then consume it, but I think an actual use of this might be misguided. Composing Writer with ListT might (would?) be bad; Writer pretty much guarantees space leaks, and ListT is meant for streaming. If someone is ever using the MonadWriter instance for something like ListT, they are likely to be doing something poorly.
Not sure if this instance should exist anymore.
| pure (go p' $! mappend w w') ) | ||
| Step (a :> rest) -> Step ( (a,w) :> go rest w) | ||
| pass l = Select (go (enumerate l) mempty) |
Uh oh!
There was an error while loading. Please reload this page.
treeowl
commented
Oct 3, 2018
Don't forget to revert all the |
chessai
commented
Oct 3, 2018
I thought I did? |
treeowl
commented
Oct 3, 2018
via email
But you did not.
git checkout master src/Streaming/Prelude.hs
and then commit. …On Wed, Oct 3, 2018, 7:04 PM chessai ***@***.***> wrote:
I thought I did?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABzi_dwk32pInoCnjG2Nn9a8ZDfRY45oks5uhUKMgaJpZM4XFL5u>
.
|
PierreR
commented
Oct 5, 2018
chessai
commented
Oct 10, 2018
Yes, if this is approved, the README change will be the last commit to occur. Thanks for pointing this out. |
I'm against depending on "exceptions" in the main "streaming" package. I would prefer the package to remain agnostic about exception and resource handling, even at the cost of some inconvenience. |
chessai
commented
Oct 22, 2018
Understandable, it would be nice if more people weighed in on this. |
chessai
commented
Oct 22, 2018
I apologise for the spam - last night's outage caused GitHub to report that i was unable to comment, i hit the comment button multiple times. I guess after things got better, all copies of the comment went through. |
masaeedu
commented
May 23, 2020
Are the unresolved questions still unresolved? |
chessai
commented
May 25, 2020
My current personal answer to the questions is No, No, and No. Maybe others have thoughts? |
danidiaz
commented
May 25, 2020
I agree with the triple-no. The |
This 2014 post by Gabriel Gonzalez gives examples of how concatenation-based |
Relevant issue: #54
Don't merge yet, some unresolved questions: