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.
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
Allow .. to be parsed as let initializer #105701
Allow .. to be parsed as let initializer #105701
Changes from 1 commit
c4d0c91
4af9e6a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
My immediate expectation would be that
parse_prefix_expr
includesparse_prefix_range_expr
. Are there any cases where we useparse_prefix_expr
and we want prefix range expressions to be an error? If yes, make sure there's a test for that; if no, then it's probably better to move the range separator check/parse insideparse_prefix_expr
.I've not looked at this code much, but the reason it might matter is for other operator precedence reasons; e.g. what's the correct result of parsing
+..1
or1+..1
.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 this separation of prefix range parsing from other prefix expr parsing is done to prevent expressions such as
-..1
or!..1
from being parsed. Other unary operators can be stacked (may not be typeable), but you cannot have..
or..=
after a unary operator.