Thanks for catching this. I've merged the pull request and replaced `atEndOfParserInput` with something else as suggested. However, I avoided making the same change as the linked commit from `pipes-binary` as I realized that it introduced a bug too: leading empty chunks are not being skipped anymore. Silly me. I'll fix that too.
I'm trying to add a test case that covers the scenario Michael encountered and then I'll upload `pipes-attoparsec-0.4.1` to Hackage including this fix. Regards, Renzo Carbonara. On Sat, Mar 15, 2014 at 7:06 PM, Patrick Wheeler <[email protected]> wrote: > @Pierre - looks like you are right, it looks like it can be done away with > completely.. > > > On Sat, Mar 15, 2014 at 5:03 PM, Pierre R <[email protected]> wrote: >> >> Good catch. By the way, I believe `atEndOfParserInput` can be removed >> similar to what has been done in pipes-binary: >> >> >> https://github.com/k0001/pipes-binary/commit/0930cb07738b5754f53e230e93dddfec463bee4d >> >> -- >> 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]. > > > > > -- > Patrick Wheeler > [email protected] > [email protected] > [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]. -- 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].
