Clarify Number precision as significant digits#44562
Open
Juke-99 wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
Content:JS
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Clarify the precision description for JavaScript
Number.This changes "about 15 to 17 decimal places" to wording that describes the precision as approximately 15–17 significant decimal digits.
Motivation
The current wording says "decimal places", but the surrounding explanation is about the precision of the mantissa/significand.
This precision is not a fixed number of digits after the decimal point. It is better described as significant decimal digits. For example, larger integer values can lose unit precision even without any fractional digits.
This change helps avoid the impression that
Numberalways preserves 15–17 digits after the decimal point regardless of the magnitude of the value.Additional details
A corresponding Japanese translation update is planned for
mdn/translated-content.Related issues and pull requests
Relates to mdn/translated-content#36668