-
-
Notifications
You must be signed in to change notification settings - Fork 406
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 by Bors] - Fixed assignment expression parsing #2268
Conversation
Test262 conformance changesVM implementation
|
Codecov Report
@@ Coverage Diff @@
## main #2268 +/- ##
=======================================
Coverage 41.33% 41.33%
=======================================
Files 234 234
Lines 22019 22021 +2
=======================================
+ Hits 9101 9102 +1
- Misses 12918 12919 +1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Looks good
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.
LGTM!
bors r+ |
This Pull Request fixes/closes #2148. It changes the following: - When we start an assignment expression, the `/` token must be a regular expression literal. The division can only occur between expressions after the assignment operator. - Added tests for the new behaviour, taken from #2177 This overrides #2177
Pull request successfully merged into main. Build succeeded: |
This Pull Request fixes/closes #2148.
It changes the following:
/
token must be a regular expression literal. The division can only occur between expressions after the assignment operator.cursor.set_goal()
call inAssignmentExpression
parsing #2177This overrides #2177