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: More structured headers #2161

Merged
merged 3 commits into from
Apr 28, 2022
Merged

Editorial: More structured headers #2161

merged 3 commits into from
Apr 28, 2022

Conversation

ptomato
Copy link
Collaborator

@ptomato ptomato commented Apr 28, 2022

Plus a few editorial fixes around time zones, in preparation for #519.

ptomato added 3 commits April 27, 2022 17:51
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.
@ptomato ptomato requested a review from Ms2ger April 28, 2022 01:01
_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
Copy link
Collaborator Author

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
Copy link

codecov bot commented Apr 28, 2022

Codecov Report

Merging #2161 (7fc4d3b) into main (3f45dca) will not change coverage.
The diff coverage is n/a.

@@           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           
Flag Coverage Δ
test262 83.44% <ø> (ø)
tests 80.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f45dca...7fc4d3b. Read the comment docs.

@Ms2ger Ms2ger merged commit 54e4abc into main Apr 28, 2022
@Ms2ger Ms2ger deleted the more-structured-headers branch April 28, 2022 09:56
@ptomato ptomato added the spec-text Specification text involved label May 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec-text Specification text involved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants