rust-lang / rust-lang/rust

Tracking Issue for saturating `SystemTime` arithmetic

Open
#151,199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue S-tracking-unimplemented T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Feature gate: #![feature(time_saturating_systemtime)]

This is a tracking issue for https://github.com/rust-lang/libs-team/issues/718

This feature adds the following three methods to SystemTime:

  • SystemTime::saturating_add
  • SystemTime::saturating_sub
  • SystemTime::saturating_duration_since
Public API
// std::time

impl SystemTime {
    // ...

    fn saturating_add(&self, rhs: Duration) -> Self {
        self.checked_add(rhs).unwrap_or(SystemTime::MAX)
    }

    fn saturating_sub(&self, rhs: Duration) -> Self {
        self.checked_sub(rhs).unwrap_or(SystemTime::MIN)
    }

    fn saturating_duration_since(&self, rhs: Self) -> Duration {
        self.duration_since(rhs).unwrap_or(Duration::ZERO)
    }
}
Steps / History

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

  • ACP: rust-lang/libs-team#718
  • Implementation: #151200
  • Final comment period (FCP)^1
  • Stabilization PR
Unresolved Questions
  • None yet.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked implementation PR #151200, the libs-team issue #718, and the feature-lifecycle stabilization guidance referenced in the issue. Review the three SystemTime methods and their completed implementation before determining whether the remaining FCP and stabilization steps are ready; done means the tracking checklist is complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.