-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
"unexpected end of input, expecting end of input" #121
Comments
Here's another way to trigger this: passports = sepBy1 passport (try (endOfLine *> endOfLine *> pure ()) <|> (endOfLine *> eof *> pure ())) which gets rid of the
|
DK318
added a commit
to DK318/parsec
that referenced
this issue
Jan 4, 2022
DK318
added a commit
to DK318/parsec
that referenced
this issue
Jan 4, 2022
Read http://blog.ezyang.com/2014/05/parsec-try-a-or-b-considered-harmful/ By |
In particular, removing |
That's fair, but it feels like this error message falls into the category of things that "should never happen". |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Weird error message coming from parsec...
and here's the input file:
input.txt
Here's what I get:
which seems... highly counter-intuitive!
The text was updated successfully, but these errors were encountered: