Tracking Issue for `try_from_{nanos_u128,mins,hours,days,weeks}` methods on `Duration`

Feature gate: #![feature(non_panicking_duration_conversion)]

This is a tracking issue for the try_from_{nanos_u128,mins,hours,days,weeks} methods on Duration.

These methods will allow you to convert from a number of minutes, hours, etc, without having to having to check for overflows before calling the method.

Public API

impl Duration {
    pub const fn try_from_nanos_u128(nanos: u64) -> Result<Duration, DurationConversionError>;
    pub const fn try_from_weeks(weeks: u64) -> Result<Duration, DurationConversionError>;
    pub const fn try_from_days(days: u64) -> Result<Duration, DurationConversionError>;
    pub const fn try_from_hours(hours: u64) -> Result<Duration, DurationConversionError>;
    pub const fn try_from_mins(mins: u64) -> Result<Duration, DurationConversionError>;
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• ACP: rust-lang/libs-team#749
• Implementation: #153683
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• TryFromFloatSecsError is still stable, but it's a type alias to DurationConversionError now. But DurationConversionError and it's fmt::Display implementation are unstable, so fmt::Display for TryFromFloatSecsError was downgraded to unstable. Should this be changed?