-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
JsValue from primitives #1993
JsValue from primitives #1993
Conversation
This change reduces our conformance by a very large amount. The reason is the conversion for The range of an integer index in javascript is, surprisingly, [0 to 2^53), which is the max integer that is representable by an |
Codecov Report
@@ Coverage Diff @@
## main #1993 +/- ##
==========================================
- Coverage 45.89% 45.85% -0.04%
==========================================
Files 206 206
Lines 17150 17170 +20
==========================================
+ Hits 7871 7874 +3
- Misses 9279 9296 +17
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!
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.
As already mentioned in multiple comments, I don't think it's the way forward. This already silently heap-allocates with a TON of overhead many Rust stack primitives. you can already do these conversions explicitly, and there are talks for adding easier boilerplating with a trait and maybe some derives.
I'm going to close this pull request in response to the comments. |
This Pull Request fixes/closes #1994 and #1991 and depends on #1971.
It changes the following:
i128
,u128
,i64
, andu64
when converting to JsValue, always converting to BigInt