-
-
Notifications
You must be signed in to change notification settings - Fork 399
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
Spec Compliant Number.prototype.toString()
, better Number
object formating and -0
#572
Conversation
Codecov Report
@@ Coverage Diff @@
## master #572 +/- ##
==========================================
+ Coverage 70.37% 70.40% +0.03%
==========================================
Files 175 175
Lines 11145 11162 +17
==========================================
+ Hits 7843 7859 +16
- Misses 3302 3303 +1
Continue to review full report at Codecov.
|
Number
object formating and -0
Number.prototype.toString()
, better Number
object formating and -0
Number.prototype.toString()
, better Number
object formating and -0
Number.prototype.toString()
, better Number
object formating and -0
Benchmark for b78a596Click to view benchmark
|
Benchmark for db12adfClick to view benchmark
|
Benchmark for bfcfa01Click 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.
Looks very nice. Check my comments. They are mostly for my understanding :)
b36b976
to
089d900
Compare
Benchmark for f2371eeClick to view benchmark
|
This Pull Request is related to #507 .
It changes the following:
Number { numberValue }
.-0
is now-0
instead of positive0
this is done by V8 and SpiderMonkey, even though it does against the tostring spec, in REPL we are not bound by the ECMAScript spec so we can do this, it makes it easier to know if the number is a-0
or a positive0
.Number.prototype.toString()
spec compliantNumber.prototype.toString()
tests