-
-
Notifications
You must be signed in to change notification settings - Fork 407
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] - Make the wasmbind
feature of the chrono
crate optional
#2810
Conversation
wasmbind
feature of the chrono
crate optionalwasmbind
feature of the chrono
crate optional
Test262 conformance changes
|
Codecov Report
@@ Coverage Diff @@
## main #2810 +/- ##
=======================================
Coverage 51.31% 51.31%
=======================================
Files 416 416
Lines 41213 41213
=======================================
Hits 21149 21149
Misses 20064 20064
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 to me! :)
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 great!
bors r+
This Pull Request fixes/closes #2475. It changes the following: - Do not use the `wasmbind` feature by default in the `chrono` crate. This can be enabled selectively if needed. - Updated the `boa_wasm` crate to use this new approach. I'm interested on knowing if this fixes @lastmjs's issue, and on checking with the team if this is the best approach to solve it.
Pull request successfully merged into main. Build succeeded: |
wasmbind
feature of the chrono
crate optionalwasmbind
feature of the chrono
crate optional
This worked! Much appreciated |
This Pull Request fixes/closes #2475.
It changes the following:
wasmbind
feature by default in thechrono
crate. This can be enabled selectively if needed.boa_wasm
crate to use this new approach.I'm interested on knowing if this fixes @lastmjs's issue, and on checking with the team if this is the best approach to solve it.