-
Notifications
You must be signed in to change notification settings - Fork 157
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: More structured headers #2161
Conversation
IsValidISODate, GetEpochFromISOParts, ISODateTimeWithinLimits, IsValidTime, GetIANATimeZoneEpochValue, GetIANATimeZoneOffsetNanoseconds, GetIANATimeZoneNextTransition, GetIANATimeZonePreviousTransition All of these operations never return a completion record, so we can remove the corresponding assertions about completion records.
…ISOParts Some existing algorithms treated this as a BigInt and some as a mathematical value. It's really six of one, half a dozen of the other, which is more convenient. I chose BigInt because that fits with the internal EpochNanoseconds slot of Instant and ZonedDateTime being a BigInt.
These notes were missing from GetIANATimeZonePreviousTransition and GetIANATimeZoneNextTransition. All operations dealing with the implementation's internal time zone database need to have this note.
_millisecond_: an integer between 0 and 999 inclusive, | ||
_microsecond_: an integer between 0 and 999 inclusive, | ||
_nanosecond_: an integer between 0 and 999 inclusive, | ||
): a BigInt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was treated as integer
in some places and BigInt
in others. I picked BigInt
but could go either way.
Codecov Report
@@ Coverage Diff @@
## main #2161 +/- ##
=======================================
Coverage 90.03% 90.03%
=======================================
Files 19 19
Lines 10905 10905
Branches 1693 1693
=======================================
Hits 9818 9818
Misses 1073 1073
Partials 14 14
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
Plus a few editorial fixes around time zones, in preparation for #519.