On 02/15/2014 07:26 AM, Pierre R wrote:
Other little personal notes:
1. As Danny points out, I am not sure `pipes-handle` is the right name
for this library. Why not `pipes-stream` with a `Reader` module
(Consumer) and a `Writer` module (Producer)?
I agree with this.
2. I have found the signature of the `read` function to be a bit
confusing because `read` in a streaming context usually does not
involve String (particularly outside of Haskell).
Maybe I should just remove the `read`/`show` commands.
3. The library might suffer from a lack of pertinent examples. For
instance I still find `yield (f a)` to be clearer than `W.map f`
The library's purpose is primarily pedagogical. That said, I still
agree with this sentiment. I think I'll sit on this library some time
longer until the examples and documentation gel.
4` . The "naked" sentence "However, @pipes@ does not officially
support this idiom" is kind of confusing and not really helpful.
Cheers
On Saturday, February 15, 2014 3:30:36 PM UTC+1, Pierre R wrote:
On Saturday, February 15, 2014 6:33:25 AM UTC+1, Gabriel Gonzalez
wrote:
Yes, `repeatM` and `mapM_` will be added for consistency.
I am probably missing the whole point of it but why is it called
`repeatM` as it does not seem to repeat anything ?
--
You received this message because you are subscribed to the Google
Groups "Haskell Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
--
You received this message because you are subscribed to the Google Groups "Haskell
Pipes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
