A slight take on what Gregory said is that io-streams is fundamentally
about streaming IO, where is pipes can be used with any base monad,
including Identity or other pure monads -- not just ones that implement
MonadIO. So if you want to compose pure streaming operations, you would
likely prefer pipes. I think conduits works that way as well now (it
originally was also IO-only).
- jeremy
On Thu, Nov 5, 2015 at 10:33 AM, Daisuke Fujimura
Hello cafe,
Now I'm preparing a presentatio for meetup for stream processing in functional programming(in Tokyo), and my part is something like "why stream processing library".
While preparing material, I encountered the question that why io-streams is so simple comparing others, and the reason and downsides behind its simplicity. I'm guessing it's due to its resource handling strategy, but not so confident about it because I couldn't came up with a concrete example yet.
Do you know any good example where io-streams won't fit? Let me know if you have.
Thanks!
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe