All notable changes to the time project will be documented in this file.
The format is based on Keep a Changelog. This project adheres to Semantic Versioning.
- Any formattable/parsable type can now be used with the
time::serde::format_description!macro. Weekday::nth_next
- The minimum supported Rust version is now 1.65.0.
- The minimum supported Rust version is now 1.63.0.
- On Unix-based operating systems with known thread-safe environments, functions obtaining the local offset no longer require a check that the program is single-threaded. This currently includes MacOS, illumos, and NetBSD.
[ignore]component in format descriptions. Acountmodifier is required, indicating the number of bytes to ignore when parsing.[unix_timestamp]component in format descriptions. This is currently only usable withOffsetDateTime. Users can choose between seconds, milliseconds, microseconds, and nanoseconds, and whether the sign is mandatory or optional.
- The API for declaring soundness now uses stricter atomic orderings internally.
This includes the update to the format_description! macro, which was supposed to be included in
0.3.18.
- The minimum supported Rust version is now 1.62.0.
[first]and[optional]items can now be included in format descriptions. To parse this at runtime, you must use theformat_description::parse_ownedmethod.format_description::parse_borrowed- An API has been added to opt out of soundness checks for obtaining the local offset. This replaces
the previous, officially unsupported
RUSTFLAGS="--cfg unsound_local_offset". End users may calltime::util::local_offset::set_soundness(time::util::local_offset::Soundness::Unsound). This method isunsafebecause it enables undefined behavior if its safety requirements are not upheld. Note that libraries must not set this toUnsound, as it is impossible for a library to guarantee end users uphold the required invariants.
- Correctly parse offset sign when hour is zero. The parse was previously unconditionally positive, even if the sign indicated otherwise.
- Compilation is fixed for WebAssembly.
- The amount of code generated by
time::serde::format_description!is reduced if not all feature flags are active. cargo test --testsworks with any configuration of feature flags. This occurs by spawning a subprocess that passes--all-features.cargo test --docworks with most combinations of feature flags, including the default. The combination of these changes means that crater will now run ontime.libcandnum_threadsare only included as dependencies when needed. They were previously unconditionally included.
time::format_description::parse_owned, which returns anOwnedFormatItem. This avoids "lifetime hell", where all your structs now need a lifetime because a single field has one. Note that when possible, the borrowed format item (just calledFormatItem) is still preferred, as it has significantly fewer allocations. The newOwnedFormatItemis usable for both formatting and parsing, as you would expect.
- The parser for runtime format descriptions has been rewritten. A side effect of this is that some errors have slightly changed. No existing API has been altered, so this is not a breaking change. However, you may notice different errors, which are hopefully better! The parser for compile-time format descriptions has not yet been swapped out. If you notice any bugs, please file an issue.
- The minimum supported Rust version is now 1.60.0.
- The
serde-well-knownfeature flag is deprecated. The necessary features for an item to be enabled are indicated in documentation. - Feature gates have been loosened for well-known formats.
-
consts can now be provided as the format description fortime::serde::format_description!. Theconstmust be of type&[FormatItem<'_>], which is what is returned by thetime::macros::format_description!macro.const TIME_FORMAT_ALT: &[FormatItem<'_>] = time::macros::format_description!("[hour]:[minute]"); time::serde::format_description!(time_format_alt, Time, TIME_FORMAT_ALT);
- Some feature flags have been removed. None of these have ever been documented as flags, so any use
was unsupported. These flags are:
js-sysquickcheck-depitoatime-macros
- Better gating for
tm_gmtoffextension. This should eliminate build failures on some untested platforms. Debugoutput for types are now human-readable. While this should not be relied upon, it is currently the same as the output withDisplay.- Eliminate overflows in the constructors for `Duration. When there is an overflow, the methods now panic. This was previously only the case in debug mode.
- Panic if
NaNis passed toDuration::from_secs_f32orDuration::from_secs_f64.
- Fix error when deserializing data types from bytes. This affects formats such as JSON.
- Eliminate a panic in an edge case when converting
OffsetDateTimeto anotherUtcOffset. This occurred due to an old assumption in code that was no longer the case.
- The minimum supported Rust version is now 1.59.0.
Duration::unsigned_absis nowconst fn.- The const parameter for
time::format_description::well_known::Iso8601now has a default. This meansIso8601is the same asIso8601::DEFAULT. - The
Parsedstruct has been reduced in size from 56 to 32 bytes (a 43% reduction).
- wasm builds other than those using
wasm-bindgenwork again.
js-sysnow supports obtaining the system's local UTC offset.
- Performance of many
Dateoperations has improved when using thelarge-datesfeature. - While an internal change,
OffsetDateTimenow stores the value in the attachedUtcOffset, not UTC. This leads to significant performance gains on nearly allOffsetDateTimemethods.
- Subtracting two
Times can no longer panic. This previously occurred in some situations where the result was invalid. - ISO 8601 parsing rounds the subseconds to avoid incorrectly truncating the value.
- [#479]: regression when parsing optional values with
serde - [#481]:
Timesubtracted fromTimecan panic. This was caused by a bug that has always existed, in that an internal invariant was not upheld. Memory safety was not violated.
- Serde support for non-self-describing formats
Duration::unsigned_abs, which returns astd::time::Duration- ISO 8601 well-known format
Durationcan now be formatted with a.Nspecifier, providing a shorter representation when usingDisplay.- Parse
nullasNoneon serde structs
- Fix incorrect parsing of UTC offset in
Rfc3339.
- The minimum supported Rust version is now 1.57.0.
- Performance for
Rfc2822has been improved. - Debug assertions have been added in a few places. This should have no user facing impact, as it only serves to catch bugs and is disabled in release mode.
time::serde::format_description!- This macro is similar to
time::format_description!, but it generates a module that can be used in#[serde(with = "foo")]. This makes it far easier to serialize/deserialize a custom format.
- This macro is similar to
Date::replace_yearDate::replace_monthDate::replace_dayTime::replace_hourTime::replace_minuteTime::replace_secondTime::replace_millisecondTime::replace_microsecondTime::replace_nanosecondPrimitiveDateTime::replace_yearPrimitiveDateTime::replace_monthPrimitiveDateTime::replace_dayPrimitiveDateTime::replace_hourPrimitiveDateTime::replace_minutePrimitiveDateTime::replace_secondPrimitiveDateTime::replace_millisecondPrimitiveDateTime::replace_microsecondPrimitiveDateTime::replace_nanosecondOffsetDateTime::replace_yearOffsetDateTime::replace_monthOffsetDateTime::replace_dayOffsetDateTime::replace_hourOffsetDateTime::replace_minuteOffsetDateTime::replace_secondOffsetDateTime::replace_millisecondOffsetDateTime::replace_microsecondOffsetDateTime::replace_nanosecondParsed::offset_minute_signedParsed::offset_second_signedParsed::set_offset_minute_signedParsed::set_offset_second_signedParsed::with_offset_minute_signedParsed::with_offset_second_signederror::InvalidVariantimpl FromStrforWeekdayimpl FromStrforMonthimpl Display for Duration
The following methods have been deprecated in favor of the new, signed equivalent methods. The pre-existing methods
Parsed::offset_minuteParsed::offset_secondParsed::set_offset_minuteParsed::set_offset_secondParsed::with_offset_minuteParsed::with_offset_second
- Well-known formats that support leap seconds now return the
TryFromParsed::ComponentRangeerror variant if the leap second could not occur at that given moment.
This release is broken and has been yanked.
Solaris and Illumos build again.
Date::saturating_addDate::saturating_subPrimitiveDateTime::saturating_addPrimitiveDateTime::saturating_subOffsetDateTime::saturating_addOffsetDateTime::saturating_subPrimitiveDatetime::MINPrimitiveDatetime::MAXRfc2822format description- Serde support for well-known formats
- This is placed behind the new
serde-well-knownfeature flag.
- This is placed behind the new
- MacOS and FreeBSD are supported obtaining the local offset when single-threaded.
- Starting with this version, this is delegated to the
num_threadscrate.
- Starting with this version, this is delegated to the
- Leap seconds are now parsed as the final nanosecond of the preceding second.
- The minimum supported Rust version is now 1.53.0.
- Deserializers for human readable formats will fall back to the binary format if the human readable format fails to deserialize.
- Deserialization will no longer fail when given a non-borrowed string.
Date::checked_addDate::checked_subPrimitiveDateTime::checked_addPrimitiveDateTime::checked_subOffsetDateTime::checked_addOffsetDateTime::checked_sub
- Attempts to obtain the local UTC offset will now succeed on Linux if the process is
single-threaded. This does not affect other Unix platforms. As a reminder, the relevant methods
are fallible and may return an
Errvalue for any reason.
error::DifferentVariantandError::DifferentVariantimpl From<Component> for FormatItem<'_>impl TryFrom<FormatItem<'_>> for Componentimpl<'a> From<&'a [FormatItem<'_>]> for FormatItem<'a>impl<'a> TryFrom<FormatItem<'a>> for &[FormatItem<'a>]impl PartialEq<Component> for FormatItem<'_>impl PartialEq<FormatItem<'_>> for Componentimpl PartialEq<&[FormatItem<'_>]> for FormatItem<'_>impl PartialEq<FormatItem<'_>> for &[FormatItem<'_>]impl TryFrom<Error> for error::TryFromParsedimpl TryFrom<Error> for error::Parseimpl TryFrom<Error> for error::ParseFromDescriptionimpl TryFrom<Error> for error::InvalidFormatDescriptionimpl TryFrom<Error> for error::IndeterminateOffsetimpl TryFrom<Error> for error::Formatimpl TryFrom<Error> for error::ConversionRangeimpl TryFrom<Error> for error::ComponentRangeimpl TryFrom<error::TryFromParsed> for error::ComponentRangeimpl TryFrom<error::Parse> for error::TryFromParsedimpl TryFrom<error::Parse> for error::ParseFromDescriptionimpl TryFrom<error::Format> for std::io::Errorimpl Sum for Durationimpl Sum<&Duration> for Duration- A
const fn default()has been added to all modifiers that arestructs. These methods exist to permit construction inconstcontexts and may be removed (without being considered a breaking change) onceimpl const Defaultis stabilized. FormatItem::Optional, which will consume the contained value if present but still succeed otherwise.FormatItem::First, which will consume the first successful parse, ignoring any prior errors.
- Cross-building to Windows now succeeds.
- A parse error on a
UtcOffsetcomponent now indicates the error comes from the offset. - Some arithmetic no longer panics in edge cases.
Parsed::parse_itemParsed::parse_itemsParsed::parse_literal- Builder methods for
Parsed - The
format_description!macro now supports thecase_sensitivemodifier.
The minimum supported version is now 1.51.0.
Instantis now#[repr(transparent)]
- Constructing a
Datefrom its ISO year, week, and weekday now returns the correct value in all circumstances. Previously, dates with an ISO year less than zero may have returned incorrect values. This affects both theDate::from_iso_week_datemethod and thedate!macro.
Monthnow implementsTryFrom<u8>From<Month>is now implemented foru8- The parser now accepts "5 PM" and similar as a valid time. Only the 12-hour clock hour and the AM/PM suffix may be present; any other components representing a time will cause an error (this exact behavior is not guaranteed).
- The
time!macro accepts the "5 PM" syntax with the same restriction.
- Macros that have a time component (
time!anddatetime!) no longer accept "0:00 AM" and similar. This was previously erroneously accepted.
datetime!macro, which allows the construction of a statically verifiedPrimitiveDateTimeorOffsetDateTime.PrimitiveDateTime::replace_timePrimitiveDateTime::replace_dateOffsetDateTime::replace_timeOffsetDateTime::replace_dateOffsetDateTime::replace_date_timeOffsetDateTime::replace_offset#![no_alloc]supportDate::to_iso_week_date, replacingDate::iso_year_weekDate::MINDate::MAXUtcOffset::from_hmsUtcOffset::from_whole_secondsUtcOffset::as_hmsUtcOffset::whole_hoursUtcOffset::whole_minutesUtcOffset::minutes_past_hourUtcOffset::seconds_past_minuteUtcOffset::is_utcUtcOffset::is_positiveUtcOffset::is_negativeOffsetDateTime::sunday_based_weekOffsetDateTime::monday_based_weekPrimitiveDateTime::to_calendar_datePrimitiveDateTime::to_ordinal_datePrimitiveDateTime::to_iso_week_datePrimitiveDateTime::to_julian_dayOffsetDateTime::to_calendar_dateOffsetDateTime::to_ordinal_dateOffsetDateTime::to_iso_week_dateOffsetDateTime::to_julian_dayTime::as_hmsTime::as_hms_milliTime::as_hms_microTime::as_hms_nanoPrimitiveDateTime::as_hmsPrimitiveDateTime::as_hms_milliPrimitiveDateTime::as_hms_microPrimitiveDateTime::as_hms_nanoOffsetDateTime::to_hmsOffsetDateTime::to_hms_milliOffsetDateTime::to_hms_microOffsetDateTime::to_hms_nanoDuration::saturating_addDuration::saturating_subDuration::saturating_mulutil::days_in_year_monthMonthInstant::into_innerimpl AsRef<StdInstant>andimpl Borrow<StdInstant>forInstant- Support for obtaining the local UTC offset on Unix-like systems has been re-added under a
user-provided flag. This functionality is not tested in any way and is not guaranteed to work.
Library authors are unable to enable this feature, as it must be passed via
RUSTFLAGS. Further information is available in the documentation.
- The minimum supported Rust version is now 1.48.0. Per the policy in the README, this may be bumped within the 0.3 series without being a breaking change.
- rand has been updated to 0.8.
- quickcheck has been updated to 1.0.
- Macros are placed behind the
macrosfeature flag. - Renamed
OffsetDatetime::timestamp→OffsetDateTime::unix_timestampOffsetDatetime::timestamp_nanos→OffsetDateTime::unix_timestamp_nanosDate::try_from_ymd→Date::from_calendar_dateDate::try_from_yo→Date::from_ordinal_dateDate::try_from_iso_ywd→Date::from_iso_week_dateDate::as_ymd→Date::to_calendar_dateDate::as_yo→Date::to_ordinal_dateDate::try_with_hms→Date::with_hmsDate::try_with_hms_milli→Date::with_hms_milliDate::try_with_hms_micro→Date::with_hms_microDate::try_with_hms_nano→Date::with_hms_nanoTime::try_from_hms→Time::from_hmsTime::try_from_hms_milli→Time::from_hms_milliTime::try_from_hms_micro→Time::from_hms_microTime::try_from_hms_nano→Time::from_hms_nanoUtcOffset::try_local_offset_at→UtcOffset::local_offset_atUtcOffset::as_seconds→UtcOffset::whole_secondsOffsetDateTime::try_now_local→OffsetDateTime::now_localDate::week→Date::iso_weekPrimitiveDateTime::week→PrimitiveDateTime::iso_weekOffsetDateTime::week→OffsetDateTime::iso_weekDate::julian_day→Date::to_julian_day- All
Durationunit values, as well as the minimum and maximum, are now associated constants. OffsetDateTime::unix_epoch()→OffsetDateTime::UNIX_EPOCHTime::midnight()→Time::MIDNIGHT
- Now
const fn(on at least newer compilers)Date::weekdayDate::next_dayDate::previous_dayPrimitiveDateTime::assume_offsetPrimitiveDateTime::weekdayDuration::checked_addDuration::checked_subDuration::checked_mulOffsetDateTime::from_unix_timestampOffsetDateTime::from_unix_timestamp_nanosOffsetDateTime::dateOffsetDateTime::timeOffsetDateTime::yearOffsetDateTime::monthOffsetDateTime::dayOffsetDateTime::ordinalOffsetDateTime::to_iso_week_dateOffsetDateTime::weekOffsetDateTime::weekdayOffsetDateTime::hourOffsetDateTime::minuteOffsetDateTime::secondOffsetDateTime::millisecondOffsetDateTime::microsecondOffsetDateTime::nanosecondOffsetDateTime::unix_timestampOffsetDateTime::unix_timestamp_nanos
- The following functions now return a
Result:Date::from_julian_dayOffsetDateTime::from_unix_timestampOffsetDateTime::from_unix_timestamp_nanos
- The following functions now return an
Option:Date::next_dayDate::previous_day
- The range of valid years has changed. By default, it is ±9999. When using the
large-datesfeature, this is increased to ±999,999. Enabling the feature has performance implications and introduces ambiguities when parsing. - The following are now gated under the
local-offsetfeature:UtcOffset::local_offset_atOffsetDateTime::now_local
Instantis now guaranteed to be represented as a tuple struct containing astd::time::Instant.- Macros are guaranteed to be evaluated at compile time.
Date::to_julian_daynow returns ani32(wasi64).Date::from_julian_daynow accepts ani32(wasi64).- Extension traits are only implemented for some types and are now sealed. As they are intended to be used with value literals, the breakage caused by this should be minimal.
- The new
Monthenum is used instead of numerical values where appropriate.
- v0.1 APIs, previously behind an enabled-by-default feature flag
PreciseTimeSteadyTimeprecise_time_nsprecise_time_sInstant::toDuration::num_weeksDuration::num_daysDuration::num_hoursDuration::num_minutesDuration::num_secondsDuration::num_millisecondsDuration::num_microsecondsDuration::num_nanosecondsDuration::spanDuration::from_stdDuration::to_std
- Panicking APIs, previously behind a non-default feature flag
Date::from_ymdDate::from_yoDate::from_iso_ywdDate::with_hmsDate::with_hms_milliDate::with_hms_microDate::with_hms_nanoTime::from_hmsTime::from_hms_milliTime::from_hms_microTime::from_hms_nano
- APIs that assumed an offset of UTC, previously enabled unconditionally
Date::todayTime::nowPrimitiveDateTime::nowPrimitiveDateTime::unix_epochPrimitiveDateTime::from_unix_timestampPrimitiveDateTime::timestampOffsetDateTime::nowimpl Sub<SystemTime> for PrimitiveDateTimeimpl Sub<PrimitiveDateTime> for SystemTimeimpl PartialEq<SystemTime> for PrimitiveDateTimeimpl PartialEq<PrimitiveDateTime> for SystemTimeimpl PartialOrd<SystemTime> for PrimitiveDateTimeimpl PartialOrd<PrimitiveDateTime> for SystemTimeimpl From<SystemTime> for PrimitiveDateTimeimpl From<PrimitiveDateTime> for SystemTimeUtcOffset::local_offset_at— assumed UTC if unable to determine local offsetOffsetDateTime::now_local— assumed UTC if unable to determine local offset
- Other APIs deprecated during the course of 0.2, previously enabled unconditionally
Duration::signPrimitiveDateTime::using_offsetSign
- Re-exports of APIs moved during the course of 0.2
days_in_yearis_leap_yearvalidate_format_stringweeks_in_yearComponentRangeErrorConversionRangeErrorIndeterminateOffsetErrorParseErrorNumericalDurationNumericalStdDurationNumericalStdDurationShort- All top-level macros
- Lazy formatting, which was unidiomatic as a failure would have returned
fmt::Error, indicating an error unrelated to the time crate.Time::lazy_formatDate::lazy_formatUtcOffset::lazy_formatPrimitiveDateTime::lazy_formatOffsetDateTime::lazy_format
- Support for stdweb has been removed, as the crate is unmaintained.
- The
preludemodule has been removed in its entirety. Date::iso_year_weekin favor ofDate::to_iso_week_datePrimitiveDateTime::iso_year_weekOffsetDateTime::iso_year_weekUtcOffset::east_hoursUtcOffset::west_hoursUtcOffset::hoursUtcOffset::east_minutesUtcOffset::west_minutesUtcOffset::minutesUtcOffset::east_secondsUtcOffset::west_secondsUtcOffset::secondsDate::month_dayPrimitiveDateTime::month_dayOffsetDateTime::month_dayWeekday::iso_weekday_number(identical toWeekday::number_from_monday)ext::NumericalStdDurationShort
- #316, where the build script was wrongly unable to determine the correct compiler version
- Dependencies have been bumped to the latest patch version, ensuring compatibility.
- Fix #309, which can cause panics in certain situations.
- The implementation of
OffsetDateTime::timestamp,OffsetDateTime::unix_timestamp,PrimitiveDatetime::timestamp, andOffsetDateTime::unix_timestamphave been corrected. This affects all negative timestamps with a nonzero subsecond value.
Due to #293, any method that requires knowledge of the local offset will now
fail on Linux. For try_ methods, this means returning an error. For others,
it means assuming UTC.
UtcOffset::timestamp(moved toUtcOffset::unix_timestamp)UtcOffset::timestamp_nanos(moved toUtcOffset::unix_timestamp_nanos)date(moved tomacros::date)time(moved tomacros::time)offset(moved tomacros::offset)OffsetDateTime::now_local(assumes UTC if unable to be determined)UtcOffset::local_offset_at(assumes UTC if unable to be determined)UtcOffset::current_local_offset(assumes UTC if unable to be determined)
- Solaris & Illumos now successfully build.
Duration::newcould previously result in an inconsistent internal state. This led to some odd situations where aDurationcould be both positive and negative. This has been fixed such that the internal state maintains its invariants.
- Implementation details of some error types have been exposed. This means that data about a component being out of range can be directly obtained, while an invalid offset or conversion error is guaranteed to be a zero-sized type.
- The following functions are
const fnon rustc ≥ 1.46:Date::try_from_iso_ywdDate::iso_year_weekDate::weekDate::sunday_based_weekDate::monday_based_weekDate::try_with_hmsDate::try_with_hms_milliDate::try_with_hms_microDate::try_with_hms_nanoPrimitiveDateTime::iso_year_weekPrimitiveDateTime::weekPrimitiveDateTime::sunday_based_weekPrimitiveDateTime::monday_based_weekutil::weeks_in_year
OffsetDateTime::timestamp_nanosOffsetDateTime::from_unix_timestamp_nanos
A bug with far-reaching consequences has been fixed. See #276 for complete details, but the gist is
that the constructing a Date from a valid Julian day may result in an invalid value or even panic.
As a consequence of implementation details, this affects nearly all arithmetic with Dates (and as
a result also PrimitiveDateTimes and OffsetDateTimes).
- Document how to construct an
OffsetDateTimefrom a timestamp-nanosecond pair
- The build script now declares a dependency on the
COMPILING_UNDER_CARGO_WEBenvironment variable. - Parsing the
%Dspecifier no longer requires padding on the month. Previously,Err(InvalidMonth)was incorrectly returned. - A
std::time::Durationthat is larger thantime::Duration::max_value()now correctly returnsOrdering::Greaterwhen compared. - Multiplying and assigning an integer by
Sign::Zeronow sets the integer to be zero. This previously left the integer unmodified.
- The following functions are
const fnon rustc ≥ 1.46:Date::try_from_ymdDate::try_from_yoTime::try_from_hmsTime::try_from_hms_milliTime::try_from_hms_microTime::try_from_hms_nano
- An
errormodule has been created where all existing error types are contained. TheErrorsuffix has been dropped from these types. - An
extmodule has been created where extension traits are contained. - A
utilmodule has been created where utility functions are contained. error::ComponentRangenow implementsCopy.
For back-compatibility, all items that were moved to newly-contained modules have been re-exported
from their previous locations (and in the case of the error module, with their previous name).
Parsing format::Rfc3339 now correctly handles the UTC offset (#274).
The following functions are const fn on rustc ≥ 1.46:
Date::yearDate::monthDate::dayDate::month_dayDate::ordinalDate::as_ymdDate::as_yoDate::julian_dayDuration::checked_divPrimitiveDateTime::yearPrimitiveDateTime::monthPrimitiveDateTime::dayPrimitiveDateTime::month_dayPrimitiveDateTime::ordinalWeekday::previousWeekday::next
size_of::<Date>()has been reduced from 8 to 4. As a consequence,size_of::<PrimitiveDatetime>()went from 16 to 12 andsize_of::<OffsetDateTime>()from 20 to 16. This change also results in a performance improvement of approximately 30% on theDate::yearandDate::ordinalmethods.cfg-ifhas been removed as a dependency.
cfgflags passed to rustc will no longer collide with other crates (at least unless they're doing something very stupid).- The crate will successfully compile with any combination of feature flags. Previously, some combinations would fail.
OffsetDateTimes can now be represented as Unix timestamps with serde. To do this, you can use the
time::serde::timestamp and time::serde::timestamp::option modules.
cargo-web support works, and is now explicitly checked in CI. A previous change was made that made
a method call ambiguous.
Adding/subtracting a core::time::Duration now correctly takes subsecond values into account. This
also affects PrimitiveDateTime and OffsetDateTime.
Panicking APIs are re-exposed.
Subtracting Instants can correctly result in a negative duration, rather than resulting in the
absolute value of it.
OffsetDateTime::now_utc
OffsetDateTime::nowdue to the offset not being clear from the method name alone.
Dates are now uniformly random when using the rand crate. Previously, both the year and day
within the year were uniform, but this meant that any given day in a leap year was slightly less
likely to be chosen than a day in a non-leap year.
- MSRV is lowered to 1.32.0.
- Support for formatting and parsing
OffsetDateTimes as RFC3339. - Lazy formatting. To avoid exposing implementation details, we're just returning
impl Display, rather than a concrete type. - Add support for Illumos.
- Deprecated APIs from time v0.1 are public again. They were previously hidden by accident in 0.2.9.
cfg-if now has a mandatory minimum of 0.1.10, rather than just 0.1. This is because compilation
fails when using 0.1.9.
cargo_websupport has been added for getting a local offset. A general catch-all defaulting to UTC has also been added.Error::sourcehas been implemented for the wrappertime::Error.UtcOffset::try_local_offset,UtcOffset::try_current_local_offset,OffsetDateTime::try_now_local()provide fallible alternatives when the default of UTC is not desired. To facilitate this change,IndeterminateOffsetErrorhas been added.- Support for parsing and formatting subsecond nanoseconds.
#[non_exhaustive]is simulated on compilers prior to 1.40.0.
Displayhas been implemented forDate,OffsetDateTime,PrimitiveDateTime,Time,UtcOffset, andWeekday.Hashis now derived forDuration.SystemTimecan be converted to and fromOffsetDateTime. The following trait implementations have been made for interoperability:impl Sub<SystemTime> for OffsetDateTimeimpl Sub<OffsetDateTime> for SystemTimeimpl PartialEq<SystemTime> for OffsetDateTimeimpl PartialEq<OffsetDateTime> for SystemTimeimpl PartialOrd<SystemTime> for OffsetDateTimeimpl PartialOrd<OffsetDateTime> for SystemTimeimpl From<SystemTime> for OffsetDateTimeimpl From<OffsetDateTime> for SystemTime
- All structs now
impl Duration<T> for Standard, allowing usage with therandcrate. This is gated behind therandfeature flag. - Documentation can now be built on stable. Some annotations will be missing if you do this.
NumericalDurationhas been implemented forf32andf64.NumericalStdDurationandNumericalStdDurationShorthave been implemented forf64only.UtcOffset::local_offset_at(OffsetDateTime), which will obtain the system's local offset at the provided moment in time.OffsetDateTime::now_local()is equivalent to callingOffsetDateTime::now().to_offset(UtcOffset::local_offset_at(OffsetDateTime::now()))(but more efficient).UtcOffset::current_local_offset()will return the equivalent ofOffsetDateTime::now_local().offset().
- All formatting and parsing methods now accept
impl AsRef<str>as parameters, rather than just&str.time::validate_format_stringdoes this as well. - The requirement of a
Datebeing between the years -100,000 and +100,000 (inclusive) is now strictly enforced. - Overflow checks for
Durationare now enabled by default. This behavior is the identical to what the standard library does. - The
time,date, andoffsetmacros have been added to the prelude.
-
Signhas been deprecated in its entirety, along withDuration::sign.To obtain the sign of a
Duration, you can use theDuration::is_positive,Duration::is_negative, andDuration::is_zeromethods. -
A number of functions and trait implementations that implicitly assumed a timezone (generally UTC) have been deprecated. These are:
Date::todayTime::nowPrimitiveDateTime::nowPrimitiveDateTime::unix_epochPrimitiveDateTime::from_unix_timestampPrimitiveDateTime::timestampimpl Sub<SystemTime> for PrimitiveDateTimeimpl Sub<PrimitiveDateTime> for SystemTimeimpl PartialEq<SystemTime> for PrimitiveDateTimeimpl PartialEq<PrimitiveDateTime> for SystemTime>impl PartialOrd<SystemTime> for PrimitiveDateTimeimpl PartialOrd<PrimitiveDateTime> for SystemTime>impl From<SystemTime> for PrimitiveDateTimeimpl From<PrimitiveDateTime> for SystemTime
- Avoid panics when parsing an empty string (#215).
- The nanoseconds component of a
Durationis now always in range. Previously, it was possible (via addition and/or subtraction) to obtain a value that was not internally consistent. Time::parseerroneously returned anInvalidMinuteerror when it was actually the second that was invalid.Date::parse("0000-01-01", "%Y-%m-%d")incorrectly returned anErr(#221).
Prior to v0.2.7, changes were listed in GitHub releases.