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 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138
//! # hifitime 0.0.1 //! //! Precise date and time handling in Rust built on top of //! [` std::time::Duration`](https://doc.rust-lang.org/std/time/struct.Duration.html). //! 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. //! //! ## Features //! //! * 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 `TimeZone`s to represent static or very high speed reference frames (cf. //! the `tz` test in the `tests` module) //! //! 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](https://www.ietf.org/timezones/data/leap-seconds.list). //! 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](https://heasarc.gsfc.nasa.gov/cgi-bin/Tools/xTime/xTime.pl?). 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](https://goo.gl/o3KXSR), //! [2015-06-30 23:59:60](https://goo.gl/QyUyrC) and [2015-07-01 00:00:00](https://goo.gl/Y25hpn). //! //! ## Does not include //! //! * Dates only, or times only (i.e. handles only the combination of both) //! * Custom formatting of date time objects //! * An initializer from machine time //! * A simple to use `TimeZone` offset //! //! ### Note on short links //! The validation tools used generate very long URLs, which aren't supported by `rustfmt`. //! 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 `info/` between `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, <https://goo.gl/o3KXSR> becomes //! <https://goo.gl/info/o3KXSR>. //! //! ## Usage //! //! Put this in your `Cargo.toml`: //! //! ```toml //! [dependencies] //! hifitime = "0.0.1" //! ``` //! //! And add the following to your crate root: //! //! ```rust //! extern crate hifitime; //! ``` //! //! ### Examples: //! //! ```rust //! use hifitime::utc::{Utc, TimeZone, TimeSystem}; //! use hifitime::instant::Duration; //! use hifitime::julian::ModifiedJulian; //! //! let santa = Utc::new(2017, 12, 25, 01, 02, 14, 0).expect("Xmas failed"); //! //! assert_eq!( //! santa.into_instant() + Duration::new(3600, 0), //! Utc::new(2017, 12, 25, 02, 02, 14, 0) //! .expect("Xmas failed") //! .into_instant(), //! "Could not add one hour to Christmas" //! ); //! assert_eq!(format!("{}", santa), "2017-12-25T01:02:14+00:00"); //! assert_eq!( //! ModifiedJulian::from_instant(santa.into_instant()).days, //! 58112.043217592596 //! ); //! assert_eq!( //! ModifiedJulian::from_instant(santa.into_instant()).julian_days(), //! 2458112.5432175924 //! ); //! ``` //! /// The `instant` module is built on top of `std::time::Duration`. It is the basis of almost /// all computations in this library. It is the only common denominator allowing for conversions /// between Time Systems. pub mod instant; /// The `julian` module supports (Modified) Julian Days, which are heavily used in astronomy /// and its engineering friends. pub mod julian; /// The `Utc` module supports conversions between Utc and other time systems. The main advantage /// (and challenge) is the inherent support for leap seconds. Refer to module documentation for /// leap second implementation details. pub mod utc; use std::cmp::PartialOrd; use instant::Instant; use std::fmt; /// A `TimeSystem` enables the creation of system for measuring spans of time, such as UTC or Julian /// days. pub trait TimeSystem: PartialOrd { /// Use this method to convert between different `TimeSystem` implementors. fn from_instant(Instant) -> Self; /// Also use this method to convert between different `TimeSystem` implementors fn into_instant(self) -> Instant; } /// Errors handles all oddities which may occur in this library. #[derive(Debug)] pub enum Errors { /// Carry is returned when a provided function does not support time carry. For example, /// if a call to `Utc::new` receives 60 seconds and there are only 59 seconds in the provided /// date time then a Carry Error is returned as the Result. Carry, } impl fmt::Display for Errors { fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result { match *self { Errors::Carry => write!(f, "a carry error (e.g. 61 seconds)"), } } } #[test] fn error_unittest() { assert_eq!( format!("{}", Errors::Carry), "a carry error (e.g. 61 seconds)" ); }