Why does decodeWith use parse instead of parseOnly? #74

Closed
tibbe opened this Issue Mar 28, 2012 · 1 comment

Projects

None yet

1 participant

@tibbe
Contributor
tibbe commented Mar 28, 2012

From my reading of the code it seems that parsing could fail even if there's more input to consume and consuming that input could make the parse succeed. It seems to me that decodeWith should use Attoparsec.parseOnly instead of Attoparsec.parse.

@tibbe
Contributor
tibbe commented Mar 28, 2012

Nevermind, I just saw that the lazy version of parse is different from the strict one.

@tibbe tibbe closed this Mar 28, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment