-
Notifications
You must be signed in to change notification settings - Fork 163
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
Audit assertions that something is an integer #1467
Comments
Note (from duplicate issue #1635) that as per the conclusion in #1229 (comment), PrepareTemporalFields should throw on infinities, so in some cases the assertions should remain the same but the steps before them should change. |
FrankYFTang
added a commit
to FrankYFTang/proposal-temporal
that referenced
this issue
Jul 14, 2021
Fix one of the issue in tc39#1467
ptomato
pushed a commit
to FrankYFTang/proposal-temporal
that referenced
this issue
Aug 12, 2021
Fix one of the issue in tc39#1467
ptomato
pushed a commit
to FrankYFTang/proposal-temporal
that referenced
this issue
Aug 17, 2021
Fix one of the issue in tc39#1467
Verify whether this is already resolved, and close if so. |
ptomato
added a commit
that referenced
this issue
Mar 26, 2024
While looking for "is an integer" assertions (#1467), I decided to remove this one by converting the AO to have a structured header.
Ms2ger
pushed a commit
that referenced
this issue
Mar 28, 2024
While looking for "is an integer" assertions (#1467), I decided to remove this one by converting the AO to have a structured header.
ptomato
added a commit
that referenced
this issue
Apr 17, 2024
ECMA-262 settled on ℝ(StringToNumber(CodePointsToString(foo))) as the proper way to do this in ParseTimeZoneOffsetString. Adopt this in the Temporal spec as well, with a similar note about precision. This removes all uses of ToIntegerOrInfinity, so the issue about auditing all uses of it to make sure they handle infinities correctly can be closed as well. Closes: #1566 Closes: #1467
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
These assertions are probably misunderstandings left over from before ToInteger was renamed to ToIntegerOrInfinity. In most cases it is probably OK to handle infinity as well. Audit all such assertions and determine whether they should handle infinities.
(Follow up from #1426 (comment))
The text was updated successfully, but these errors were encountered: