-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
JuliaSyntax: fix anonymous function parsing #60221
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
Open
IanButterworth
wants to merge
1
commit into
JuliaLang:master
Choose a base branch
from
IanButterworth:ib/syntax
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+19
−4
Open
Changes from all commits
Commits
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
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.
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.
I think it would make a lot of sense to split the logic with a case distinction on
_maybe_grouping_parens: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.
Subsequently, it makes sense to inspect more closely what happens if
_maybe_grouping_parensis true: If the next tokens are:K")", K"NewlineWs", then we callpeek(ps, 2, skip_newlines=false) = token_after_parenK")", !K"NewlineWs", then we callpeek(ps, 2, skip_newlines=true) = token_after_paren!K")", x/*we expect K")" here, but don't check that*/, K"NewlineWs", then we callpeek(ps, 2, skip_newlines=false)=token_after_paren(I think (hope I interpret it correctly) that__lookahead_indextreats the case withskip_newlines=truesuch that it also skips newlines entirely, including in the count up ton=2)!K")", x, !K"NewlineWs", then we callpeek(ps, 2, skip_newlines=false)=token_after_paren`So, I think we can omit the
peek(ps, 2, skip_newlines= token_after_paren != K"NewlineWs")entirely.