Package dev.gmitch215.bytebox.time
java.time work, which nothing in a project has to name.
The class library has no java.time at all, so a program using a date would fail while it
was being compiled. A project writes java.time as it would anywhere, and the compiler points
those references at an implementation of the same API; the classes here are the two pieces of that
implementation the platform has to supply itself, namely where the timezone rules come from.
The rules come from Intl, which the isolate already carries, rather than from a compiled
copy of the timezone database inside the binary. IntlZoneRules
derives the rest of the interface from the one question that answers, and records the three places
where deriving is not the same as reading.
The clock is a separate matter, and Clock is the thing to
read about it: Workers pin the clock between I/O, so Instant.now() does not advance inside a
request.
- Since:
- 1.0.0
-
ClassDescriptionPoints
java.timeat an implementation of it, and its rule provider at this package's.The offset a zone was at an instant.What a zone's offset was, and when it changed.Wherejava.timegets its timezone rules.