1-based
Optionalmicrosecond: number = 0Optionalprecision: number = ...
fractional digits to display, 0..6
The reference's equality, which -key = [...] removes by: the same
datetime written to the same precision (07:32:00.5 is not
07:32:00.500, as an Elixir NaiveDateTime with a different microsecond
precision is not). It once ignored the precision, and -key removed
entries the reference keeps.
this wall-clock time, read in the local time zone
YYYY-MM-DDTHH:MM:SS[.fraction]
StaticfromStaticparseYYYY-MM-DDTHH:MM:SS[.fraction]
A date and wall-clock time with no zone or offset -- CASC.md §6.6's local datetime (
1979-05-27T07:32:00). Mirrors Elixir'sNaiveDateTime, at microsecond resolution.An offset datetime (
1979-05-27T07:32:00Z) is a real instant and loads as aDateTimeinstead -- see the README's value table.The closest native fit is a
Dateread in the process's local time zone:toDate()/LocalDateTime.fromDate()(both use local calendar fields, the same asnew Date(y, m, d, h, mi, s)does). Sub-millisecond digits don't survive the trip, sinceDatehas none.