We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Currently we use the default native Rust formatter to format floating-point numbers, which is not spec compliant.
To Reproduce Steps to reproduce the issue, or JavaScript code that causes this failure.
This JavaScript code reproduces the issue:
0.0000001 3.e50
Expected behavior
In this scenario we should get 1e-7 and 3e+50 back. Actual output is 0.0000001 and 300000000000000000000000000000000000000000000000000.
1e-7
3e+50
0.0000001
300000000000000000000000000000000000000000000000000
Build environment (please complete the following information):
Additional context
We need to write our own f64 formatter like V8 DoubleToCString (see V8 implementation link bellow)
DoubleToCString
You can find more information:
The text was updated successfully, but these errors were encountered:
I can take this if nobody else wants it :)
Sorry, something went wrong.
Sure! Tell us if you need any help, or if you have any questions
Tropid
No branches or pull requests
Describe the bug
Currently we use the default native Rust formatter to format floating-point numbers, which is not spec compliant.
To Reproduce
Steps to reproduce the issue, or JavaScript code that causes this failure.
This JavaScript code reproduces the issue:
Expected behavior
In this scenario we should get
1e-7
and3e+50
back.Actual output is
0.0000001
and300000000000000000000000000000000000000000000000000
.Build environment (please complete the following information):
Additional context
We need to write our own f64 formatter like V8
DoubleToCString
(see V8 implementation link bellow)You can find more information:
The text was updated successfully, but these errors were encountered: