-
-
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] - Allow let
as variable declaration name
#2044
Conversation
Test262 conformance changesVM implementation
Fixed tests (12):
|
Codecov Report
@@ Coverage Diff @@
## main #2044 +/- ##
==========================================
- Coverage 43.90% 43.87% -0.04%
==========================================
Files 212 212
Lines 18734 18757 +23
==========================================
+ Hits 8226 8229 +3
- Misses 10508 10528 +20
Continue to review full report at Codecov.
|
Benchmark for 4b06192Click to view benchmark
|
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.
Thanks!!
bors r+ |
Pull request successfully merged into main. Build succeeded: |
let
as variable declaration namelet
as variable declaration name
Is there a specific test for this? Or are we using Test262 in general as our testing methods? While I see the value on using Test262, it is also good to use our in-house tests in order to catch regressions. |
Unless there are implementation specific tests that are not covered by the 262 suite, I think replicating the 262 tests does not make much sense. We have to run the 262 suite anyways, so we would mostly just double the test time. Also whenever the 262 suite changes, we would have to adjust our internal test suite which would probably result in the two suites diverging. But that's just my 2 cents. |
This Pull Request changes the following:
let
as variable declaration name