-
-
Notifications
You must be signed in to change notification settings - Fork 415
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
Move require_object_coercible
to Value
#654
Conversation
Codecov Report
@@ Coverage Diff @@
## master #654 +/- ##
=======================================
Coverage 72.50% 72.50%
=======================================
Files 179 179
Lines 13376 13376
=======================================
Hits 9698 9698
Misses 3678 3678
Continue to review full report at Codecov.
|
Benchmark for 2c02efdClick to view benchmark
|
Interpreter::require_object_coercible
to Value::require_object_coercible
require_object_coercible
to Value
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, thanks!
* Added CLEAN_JS and MINI_JS benches (#581) * Added CLEAN_JS and MINI_JS benches These benches are arbitrary code which is subject to change, functionally the programs are identical. * Forgot semicolon * Adding parsing benchmarks for CleanJS & MiniJS Added identical benchmark cases for parser. * Migrating Clean and Mini benchmarks to new format Adding js scripts in bench_scripts & moving exec, full and parser benchmarks to new include_str!() macro. * Move `require_object_coercible` to `Value` (#654) Co-authored-by: neeldug <5161147+neeldug@users.noreply.github.com> Co-authored-by: HalidOdat <halidodat@gmail.com>
This is something I missed when I was moving the methods in #625 , like
to_string()
this is a value operation so it belongs inValue
.It changes the following:
Interpreter::require_object_coercible
toValue::require_object_coercible