Fix some floating-point roundoff errors #21
Merged
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
|
Can you add some tests that would have failed before these changes? |
roundTo(0.597/6, 3) === 0.1
// false
roundTo.up((0.1+0.2)*10, 0) === 3
// false
roundTo.down((0.1+0.7)*10, 0) === 8
// false |
sindresorhus
changed the title
sindresorhus
changed the title
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.
I suggest to use the toPrecision() method to preround the result to 15 significant digits. This will strip the floating-point round-off errors in the intermediate calculations.
Please refer to my answer on stackoverflow https://stackoverflow.com/a/48764436
Fixes #20