Editorial: a couple of fixes for Math #2172
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
bakkot
changed the title
bakkot
changed the title
ljharb
reviewed
Sep 13, 2020
ljharb
approved these changes
Sep 13, 2020
michaelficarra
approved these changes
Sep 14, 2020
ljharb
force-pushed
the
numbers-once
branch
from
464d064 to
575149c
Compare
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.
Followup to #2122.
The first commit, 75c3c48, makes it explicit that coercion happens exactly once for each argument to Math.hypot. See #2122 (comment).
The second commit, fb2811b, ensures that
Math.hypot(-Infinity)returnsInfinity, not-Infinity.The third commit, 464d064, ensures that all possible side effects in
Math.hypot,Math.max, andMath.minhappen before the method returns.