-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression in parsec-3.1.6 #9
Comments
This is caused by 8607649. I think that change should just be reverted for now. |
kosmikus
referenced
this issue
Sep 23, 2014
Example Before: Prelude Text.Parsec> parseTest (string "abcd") "abbe" parse error at (line 1, column 1): unexpected "b" expecting "abcd" After: *Main> parseTest (string "abcd") "abbe" parse error at (line 1, column 3): unexpected "b" expecting "cd" Before this patch, 'b' was reported to be found at 1:1, which is clearly not the case. After this patch, we correctly report the location of the wrong token, and also report missing tokens starting from that position.
aslatter
added a commit
that referenced
this issue
Sep 25, 2014
Also move test for #2 to have a more regular structure for tests aimed at specific bugs.
Thanks for the bug report. I've reverted the change, and I'll be pushing out 3.1.7 soon. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consider
with
parsec-3.1.5
and below we getbut with
parsec-3.1.6
we getThe text was updated successfully, but these errors were encountered: