Minor DateTime intro doc update
• Put timezone in the lede since it's critical. • Mention Instant and SystemTime to put DateTime in context
This commit is contained in:
parent
8efc85ce9f
commit
531aa752b3
13
README.md
13
README.md
|
@ -53,9 +53,18 @@ provided by crates.io `time` crate (which originally comes from Chrono).
|
||||||
|
|
||||||
### Date and Time
|
### Date and Time
|
||||||
|
|
||||||
Chrono provides a `DateTime` type for the combined date and time.
|
Chrono provides a
|
||||||
|
[`DateTime`](https://lifthrasiir.github.io/rust-chrono/chrono/datetime/struct.DateTime.html)
|
||||||
|
type to represent a date and a time in a timezone.
|
||||||
|
|
||||||
`DateTime`, among others, is timezone-aware and must be constructed from
|
For more abstract moment-in-time tracking such as internal timekeeping
|
||||||
|
that is unconcerned with timezones, consider
|
||||||
|
[`time::SystemTime`](https://doc.rust-lang.org/std/time/struct.SystemTime.html),
|
||||||
|
which tracks your system clock, or
|
||||||
|
[`time::Instant`](https://doc.rust-lang.org/std/time/struct.Instant.html), which
|
||||||
|
is an opaque but monotonically-increasing representation of a moment in time.
|
||||||
|
|
||||||
|
`DateTime` is timezone-aware and must be constructed from
|
||||||
the `TimeZone` object.
|
the `TimeZone` object.
|
||||||
`DateTime`s with different time zones do not mix, but can be converted to
|
`DateTime`s with different time zones do not mix, but can be converted to
|
||||||
each other using the `DateTime::with_timezone` method.
|
each other using the `DateTime::with_timezone` method.
|
||||||
|
|
Loading…
Reference in New Issue