-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Normative: Treat -0 as negative in NumberFormat #232
Conversation
Would anyone be interested in writing test262 tests for this change? @anba @jackhorton @Ms2ger |
This test would now be possible because of the required data frontmatter? Not sure how to test this other than to actually inspect the string coming out of format and/or the minusSign part coming out of formatToParts. |
The specification was updated in tc39/ecma402#232.
Test: tc39/test262#1628 |
OK, has anyone implemented this in a JS engine? Now that there's a test262 test, it should be easier to verify. |
The specification was updated in tc39/ecma402#232.
The specification was updated in tc39/ecma402#232.
@jackhorton reported in July's meeting notes that this change is implemented in ChakraCore. Between the tests, the change, and the implementation experience. this patch is ready to land. |
See #13. Merges change from tc39/ecma402#232 into Unified Intl.NumberFormat proposal.
I merged the change to the corresponding spot in my proposal. |
The spec changed in 7/2018 to treat -0 and 0 differently. tc39/ecma402#232 Bug: v8:7474, v8:8099 Change-Id: I77db4ae716b081b7628dc7ee253a463520c7f6e9 Reviewed-on: https://chromium-review.googlesource.com/c/1400403 Reviewed-by: Sathya Gunasekaran <gsathya@chromium.org> Commit-Queue: Frank Tang <ftang@chromium.org> Cr-Commit-Position: refs/heads/master@{#58645}
The specification was updated in tc39/ecma402#232.
The specification was updated in tc39/ecma402#232.
Closes #219