<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<body bgcolor="#ffffff" text="#000000">
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Subject: </th>
<td>Re: [Haskell-cafe] A home-brew iteration-alike library:
some extension quiestions</td>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">Date: </th>
<td>Thu, 09 Dec 2010 23:07:49 +0300</td>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">From: </th>
<td>Permjacov Evgeniy <a class="moz-txt-link-rfc2396E" href="mailto:firstname.lastname@example.org"><email@example.com></a></td>
<th align="RIGHT" valign="BASELINE" nowrap="nowrap">To: </th>
<td>Antoine Latter <a class="moz-txt-link-rfc2396E" href="mailto:firstname.lastname@example.org"><email@example.com></a></td>
<pre>On 12/09/2010 10:54 PM, Antoine Latter wrote:
> I only have some surface level questions/comments -
> What existing packages is this similar to? How is it different from
> any previous work in the area?
Main idea was taken from Iteratees invented by Oleg Kiselev (there are
two packages on hackage implementing this ideas: data-iteraties and
The difference is, that I wished haskell-2010 compilant package for
left-foldable streams, including support for easy builing, transcoding,
merging and folding of streams relying on do-notation (see
Data.Iteration.Unicode.* for examples of transcoding streams: it is
quite clean and easily understandable) and ability to specify easily
monadic actions in stream processors.
> Also, likes looks like you don't need the 'Monad m' constraint on your
> various Monad and Functor instances in Data.Iteration.Types, which I
> think is one of the nicest properties of the continuation-based
> approach to something like this.
Errgh. That may be true, but I did not consider non-monadic context at
all, so I enforced this constrain mindlessly
> It's a mater of taste which way to go, but I prefer importing modules
> qualified rather than have type-suffixes on functions - so I would
> rather use 'I.next' and 'A.next' instead of 'nextI' and 'nextA'. But
> reasonable people can disagree on this.
> Take care,
> On Thu, Dec 9, 2010 at 1:42 PM, Permjacov Evgeniy <a class="moz-txt-link-rfc2396E" href="mailto:firstname.lastname@example.org"><email@example.com></a> wrote:
>> Hi. I Wrote a simple iteration library. It was not intensively tested,
>> so it MAY contatin bugs, but it is very unlikely. The library is
>> currently on github: <a class="moz-txt-link-freetext" href="https://github.com/permeakra/iteration">https://github.com/permeakra/iteration</a>
>> I'm not ready to upload it to hackage, as some testing and extension is
>> really needed. However, I'd like to know about possible flaws.
>> Current goal is addition of byte-stream (de)compression and IO functions
>> extenstion. After this package will be cabalized and uploaded to
>> hackage. So, while design is not frozen yet, I'm interested in criticism -)/
>> Haskell-Cafe mailing list
>> <a class="moz-txt-link-abbreviated" href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a>
>> <a class="moz-txt-link-freetext" href="http://www.haskell.org/mailman/listinfo/haskell-cafe">http://www.haskell.org/mailman/listinfo/haskell-cafe</a>