-
Notifications
You must be signed in to change notification settings - Fork 18
Correctly parse ado without any statements in it #46
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
Merged
natefaubion
merged 4 commits into
natefaubion:main
from
MonoidMusician:muchadoaboutnothing
Mar 5, 2023
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
a517079
Correctly parse ado without any statements in it
MonoidMusician cfb0311
Tests for ado/in, with empty cases and recovery
MonoidMusician 707e8de
Inline tweaked layout helper with comments explaining why
MonoidMusician 0141b02
Update src/PureScript/CST/Parser.purs
natefaubion File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like it should be equivalent to
optional
? If we had an empty layout, then valueParser should immediately fail if given a TokLayoutEnd, shouldn't it? It's not obvious to me what "backtracking far enough" means then, and that there isn't some other internal bug. Do we know where backtracking is halting?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I was a little hasty in ascribing it to backtracking. Putting
try
in there does not help.What's really messing it up is the indentation-based parser recovery when we call it in
parseAdo
(this is the only usage oflayout
). An an example change, this manages to parse the emptyado in
:Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It makes sense to me that there is something odd with recovery, but I'm not sure what. In the case of
ado in
, I would expectrecoverIndent
to immediately hit aTokLayoutEnd
wherecol == indent
, resulting in emptytokens
, yieldingNothing
, which would propagate the error.purescript-language-cst-parser/src/PureScript/CST/Parser.purs
Lines 1155 to 1164 in 5afff30
purescript-language-cst-parser/src/PureScript/CST/Parser/Monad.purs
Lines 149 to 151 in 5afff30
Maybe something is wrong with the state threading in
recover
. The logic of the original code seems OK to me, which makes me think this is an internal bug and not related to the specific formulation of this parser.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I'll push a test for this case and dig deeper.