<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">From: <a href="mailto:dm-list-haskell-cafe@scs.stanford.edu">dm-list-haskell-cafe@scs.stanford.edu</a><br>
<br>
At Fri, 6 May 2011 10:10:26 -0300,<br>
Felipe Almeida Lessa wrote:<br>
<br>
> So, in the enumerator vs. iterIO challenge, the only big differences I see are:<br>
><br>
> a) iterIO has a different exception handling mechanism.<br>
> b) iterIO can have pure iteratees that don't touch the monad.<br>
> c) iterIO's iteratees can send control messages to ther enumerators.<br>
> d) iterIO's enumerators are enumeratees, but enumerator's enumerators<br>
> are simpler.<br>
> e) enumerator has fewer dependencies.<br>
> f) enumerator uses conventional nomenclature.<br>
> g) enumerator is Haskell 98, while iterIO needs many extensions (e.g.<br>
> MPTC and functional dependencies).<br>
><br>
> Anything that I missed?<br>
><br>
> The bottomline: the biggest advantage I see right now in favor of<br>
> iterIO is c),<br>
<br>
I basically agree with this list, but think you are underestimating<br>
the value of a. I would rank a as the most important difference<br>
between the packages. (a also is the reason for d.)<br></blockquote><div><br></div><div>'a' is important, but I think a lot of people underestimate the value of 'c', which is why a control system was implemented in 'iteratee'. I would argue that iteratee's control system is more powerful than you say. For example, the only reason iteratee can't implement tell is because it doesn't keep track of the position in the stream, it's relatively simple for an enumerator to return data to an iteratee using an IORef for example. And adding support to keep track of the stream position would be a pretty simple (and possibly desirable) change. But it's definitely not as sophisticated as IterIO, and probably won't become so unless I have need of those features.</div>
<div><br></div><div>I like the MonadTrans implementation a lot. The vast majority of iteratees are pure, and GHC typically produces more efficient code for pure functions, so this is possibly a performance win. Although it makes something like the mutable-iter package very difficult to implement...</div>
<div><br></div><div>John Lato</div></div>