fix(#74): use normalized notation on toStringAsExponential #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
canastro
changed the title
canastro
changed the title
|
Thanks for the report and this fix ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few releases ago Decimal was using Doubles to perform
toStringAsExponential:This approach seems to use the normalized scientific notation, ie: given dec('9.9999e+7').toStringAsExponential(2) it would output 1.00e+8.
With the current implementation that same input will return 10.00e+7.
Let me know if you consider this a bug and its a fix you want to merge.
Fixes #74