finetime 0.8.1

High-fidelity time library for applications where sub-nanosecond accuracy and exact arithmetic are needed
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

//! Implementation of timekeeping according to different time scales.

mod convert;
pub use convert::{FromTimeScale, IntoTimeScale};
mod datetime;
pub use datetime::{
    FromDateTime, FromFineDateTime, IntoDateTime, IntoFineDateTime, UniformDateTimeScale,
};

mod bdt;
pub use bdt::{Bdt, BeiDouTime};
mod glonasst;
pub use glonasst::{GlonassTime, Glonasst};
mod gpst;
pub use gpst::{GpsTime, Gpst};
mod gst;
pub use gst::{GalileoTime, Gst};
mod leap_seconds;
pub use leap_seconds::{
    FromLeapSecondDateTime, IntoLeapSecondDateTime, LeapSecondProvider,
    STATIC_LEAP_SECOND_PROVIDER, StaticLeapSecondProvider,
};
mod qzsst;
pub use qzsst::{QzssTime, Qzsst};
mod tai;
pub use tai::{Tai, TaiTime};
mod tcg;
pub use tcg::{Tcg, TcgTime};
mod tt;
pub use tt::{Tt, TtTime};
mod terrestrial_time;
pub use terrestrial_time::TerrestrialTime;
mod utc;
pub use utc::{Utc, UtcTime};

use crate::Date;

/// A `TimeScale` identifies the relativistic time scale in which some `TimePoint` is expressed.
pub trait TimeScale {
    /// The full (English) name of a time scale.
    const NAME: &'static str;

    /// The abbreviated string used to represent this time scale.
    const ABBREVIATION: &'static str;
}

/// `TimeScale` that is fixed in calendrical time by an absolute epoch. Note that this does not yet
/// unambiguously define the scale: for that, it must be linked to a well-defined scale like TAI or
/// UTC (for example, by implementing the `TerrestrialTime` trait).
pub trait AbsoluteTimeScale: TimeScale {
    /// Determines the epoch used to convert date-time of this time scale into the equivalent
    /// time-since-epoch `TimePoint` representation. For simplicity, epochs must fall on date
    /// boundaries.
    ///
    /// Note that this epoch does not bear any "real" significance: it is merely a representational
    /// choice. In principle, it may even be distinct from the "actual" epoch, if any is defined,
    /// for a time scale. For GPS, for example, the epoch is well-defined as 1980-01-06T00:00:00
    /// UTC, but it would not necessarily be wrong to use a different date here. In practice, of
    /// course, it is more convenient to choose the actual epoch where one is defined.
    const EPOCH: Date<i32>;
}