Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Why does decodeWith use parse instead of parseOnly? #74

tibbe opened this Issue · 1 comment

1 participant


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.


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

@tibbe tibbe closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.