Skip to content
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

Editorial: Next batch of minor editorial improvements #2839

Merged
merged 4 commits into from
May 15, 2024
Merged

Conversation

ptomato
Copy link
Collaborator

@ptomato ptomato commented May 14, 2024

After combining the diffing and rounding code paths, this is the only
remaining caller of AddDuration. Additionally, rename it to AddDurations
to avoid the unwieldy name.
GetNamedTimeZoneNextTransition and GetNamedTimeZonePreviousTransition had
the wrong ESIDs.
Commit 1643cc6 only changed IsValidDuration to correctly reject too-large
duration values, but the other half was that BalanceTimeDuration needs to
be able to throw when that happens.

BalanceTimeDuration can throw due to floating-point rounding error if the
normalized time duration could be nearby the limit and largestUnit is
milliseconds, microseconds, or nanoseconds.

Closes: #2785
@Ms2ger Ms2ger merged commit a113bda into main May 15, 2024
5 checks passed
@Ms2ger Ms2ger deleted the editorial branch May 15, 2024 11:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BalanceTimeDuration: CreateTimeDurationRecord can create too large duration values
2 participants