-
-
Notifications
You must be signed in to change notification settings - Fork 401
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
Fix Number.toExponential
and Number.toFixed
#1620
Conversation
Test262 conformance changes:
Fixed tests (24):
|
Regarding the one failing test; I think we should merge this without that one. But we may have an easier solution that to fix the issues in Without looking further into it, my idea would be to implement the functionality of |
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.
Just a small nitpick I have about the utility functions
Actually I just realized that there's another case which isn't covered by any 262 test and that's |
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.
Great work!
Oh, that can be filed on the test262 repo |
This Pull Request closes #1602.
It makes
toExponential
andtoFixed
methods onNumber
compliant with the specification.One of the tests in
toExponential
currently fails. This is something that's blocked by rust-lang/rust#89493, unless we were to implement the exponential string algorithm ourselves.