-
-
Notifications
You must be signed in to change notification settings - Fork 402
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] - Fix PropertyKey
to JsValue
conversion
#1886
Conversation
Test262 conformance changesVM implementation
Fixed tests (64):
|
Codecov Report
@@ Coverage Diff @@
## main #1886 +/- ##
=======================================
Coverage 46.75% 46.76%
=======================================
Files 204 204
Lines 16755 16752 -3
=======================================
Hits 7834 7834
+ Misses 8921 8918 -3
Continue to review full report at Codecov.
|
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!
Benchmark for dc17f79Click to view benchmark
|
bors r+ |
We store string `PropertyKey`s with two enums `String` and `Index` for performance reasons, but the spec does not differentiate between string and index property keys so before conversion to `JsValue` we have to convert to a string. This was failing tests like `Reflect.ownKeys([true, "", 1])` because it was returning (integer numbers) `[1, 2, 3]` instead of `['1', '2', '3']`
Pull request successfully merged into main. Build succeeded: |
PropertyKey
to JsValue
conversionPropertyKey
to JsValue
conversion
We store string
PropertyKey
s with two enumsString
andIndex
for performance reasons, but the spec does not differentiate between string and index property keys so before conversion toJsValue
we have to convert to a string.This was failing tests like
Reflect.ownKeys([true, "", 1])
because it was returning (integer numbers)[1, 2, 3]
instead of['1', '2', '3']