docs(design): add the named time zones record #476
Loading…
Reference in a new issue
No description provided.
Delete branch "loop/389-time-zones-record"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Design record for named time zones (
docs/design/TIME.md, status "designed, not built"), the last slice of gap 11 inFIRST-PARTY.md:std/timefrom one pinned tzdata release; no system zoneinfo is readTimeZoneimportsTimeZoneandZonedDateTimeare capability-free values; only reading the clock isclockDisambiguation(Earlier,Later,Reject) is a required argument wherever a local time becomes an instant, with the Berlin gap/overlap tableAlso: gap 11 in
docs/design/FIRST-PARTY.mdlinks the record;docs/design/index.mdlists it.Slices
Section 9 of the record holds the 6-slice table (fetch/generate tooling, data module,
TimeZone,ZonedDateTime+Disambiguation, RFC 9557 text, capability table + docs). Each slice is filed as an issue when the one before starts.Open points
zicbuilt from the pinnedtzcode" is proposed in this record, not an outcome of the refinement. Marked as such in section 2; to be confirmed in slice 1.Docs only;
pdisc.py checkpasses locally. No line inTIME.mdis longer than 120 columns.Closes #389
Checklist (head
2f8c36e):Non-blocking: none.