Will do! All of the mapIso variants share some code, should it be duplicated unexported in each library, or added to Pipes.Internal?
Also, some functions are postfixed by type (drawByte, nextChar, etc.), while others are not (map, drop, etc.). The reason isn't clear to me, but was your suggestion of postfixes for mapIso deliberate? kl. 00:39:50 UTC+2 onsdag 28. mai 2014 skrev Gabriel Gonzalez følgende: > > Oops, then yeah. Submit this to `pipes-parse` instead of > `pipes-extras`. That makes more sense. > > On 5/25/14, 10:06 AM, Torgeir Strand Henriksen wrote: > > Sorry, the idea was that pipeMapIsoP goes in Pipes.Parse. > -- > 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > > > -- 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].
