Precise date and time handling in Rust built on top of
The Epoch used is TAI Epoch of 01 Jan 1900 at midnight, but that should not matter in
day-to-day use of this library.
- Leap seconds (as announced by the IETF on a yearly basis)
- Julian dates and Modified Julian dates
- UTC representation with ISO8601 formatting
- Allows building custom TimeSystem (e.g. Julian days)
- Time varying
TimeZones to represent static or very high speed reference frames (cf. the
tztest in the
Almost all examples are validated with external references, as detailed on a test-by-test basis.
Leap second support
Each time computing library may decide when the extra leap second exists as explained
in the IETF leap second reference.
To ease computation,
hifitime decides that second is the 60th of a UTC date, if such exists.
Note that this second exists at a different time than defined on NASA HEASARC. That tool is
used for validation of Julian dates. As an example of how this is handled, check the Julian
day computations for 2015-06-30 23:59:59,
2015-06-30 23:59:60 and 2015-07-01 00:00:00.
Does not include
- Dates only, or times only (i.e. handles only the combination of both)
- Custom formatting of date time objects (cf. issue #4)
- An initializer from machine time (cf. issue #8)
- A simple to use TimeZone offset (cf. issue #12)
Note on short links
The validation tools used generate very long URLs, which aren't supported by
As such, whenever a validation link is provided, it has been shortened using Google's
http://goo.gl service. If this is an issue, please add
goo.gl/ and the
unique identifier: this will allow you to see the redirection link prior to being redirected
(as well as the link analytics). For example,