avm: Fix issues with parsing "inf" floats on nightly Rust #3984
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.
Rust nightly 4/13 allows f64::parse to handle "infinity", case
insensitive. This broke cases such as
Number("Infinity")
, whichshould return
NaN
in AVM1. Also,Number("inf")
incorrectlyreturned
Infinity
in both AVM1 and AVM2.Additionally, Rust will now print "-0" for negative zero, when
previously it would print "0".
Number("inf")
(this was also incorrect beforethe latest nightly)
f64_to_string
to ensurethat -0.0 gets coerced to "0".
For more info, see:
rust-lang/rfcs#1074