Yes, I was forecasting a little...

Concerning conduit, yes it's not another implementation of Oleg's iteratees, yet its API looks a lot like 'enumerators'.
Plus it aims at solving the same problem, only the implementation that differs (roughly state variables instead of pure closure-based automata)

2012/1/28 Erik de Castro Lopo <mle+hs@mega-nerd.com>
Yves Parès wrote:

> Yes, and IMO this is a growing problem. Since iteratees were designed, a
> lot of different libraries providing this kind of service have appeared.

Thats mainly because the solution space was new and lots of unexplored
terrain.

> Or else, we have to make sure that each one (iteratee, enumerator, conduit,
> pipes...) has its own set of associated packages and that each provide
> equivalent functionalities, but then => combinatorial explosion.

There really isn't a combinatorial explosion, but rather a small number
of families of packages.

> ^^ It's just I don't want people to start trolling by applying to Haskell
> the adage I've heard quite a few times about Java, stating that "There are
> 50 ways to achieve something... none of which is good".

Java has been around 20 years. The iteratee/enumerator/iterio/conduit/pipes
idea has really only been around for a couple of years and I would be
surprised it one of them (or a new one combining the best features of
the others) doesn't come out the clear winner in the next year or two.

Erik
--
----------------------------------------------------------------------
Erik de Castro Lopo
http://www.mega-nerd.com/

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe