-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Stabilize checked_duration_since for 1.39.0 #62860
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
r? @dtolnay |
Ping from Triage. @dtolnay @rust-lang/libs checking on the status of a review for this PR. |
Looks reasonable to me to merge, so let's... @rfcbot fcp merge New functions here are: impl Instant {
pub fn checked_duration_since(&self, earlier: Instant) -> Option<Duration>;
pub fn saturating_duration_since(&self, earlier: Instant) -> Duration;
} |
Team member @alexcrichton has proposed to merge this. The next step is review by the rest of the tagged team members: No concerns currently listed. Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! See this document for info about what commands tagged team members can give me. |
🔔 This is now entering its final comment period, as per the review above. 🔔 |
The final comment period, with a disposition to merge, as per the review above, is now complete. As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed. The RFC will be merged soon. |
@bors: r+ |
📌 Commit 01d9e57 has been approved by |
…, r=alexcrichton Stabilize checked_duration_since for 1.38.0 Looks like it has already found some use in projects. Resolves rust-lang#58402.
What to do now? Shall I try renaming to |
I believe if you change the line I pointed to have a feature name that is not checked_duration_since, everything should work. |
r=me with this all squashed into one or two commits (I'd personally separate out the tidy fix but doesn't matter too much) as well as a rebase |
Means "abandon this pull request and submit the new one, specifying Or just rebase and force-push in place? |
bb1bbe3
to
9d3cfae
Compare
Went with the latter. Can rollback if needed. |
9d3cfae
to
5545582
Compare
Yep, rebase and force-push is perfect. @bors r+ |
📌 Commit 5545582 has been approved by |
…, r=Mark-Simulacrum Stabilize checked_duration_since for 1.38.0 Looks like it has already found some use in projects. Resolves rust-lang#58402.
…, r=Mark-Simulacrum Stabilize checked_duration_since for 1.38.0 Looks like it has already found some use in projects. Resolves rust-lang#58402.
Rollup of 15 pull requests Successful merges: - #62860 (Stabilize checked_duration_since for 1.38.0) - #63549 (Rev::rposition counts from the wrong end) - #63985 (Stabilize pin_into_inner in 1.39.0) - #64005 (Add a `Place::is_indirect` method to determine whether a `Place` contains a `Deref` projection) - #64031 (Harden `param_attrs` test wrt. usage of a proc macro `#[attr]`) - #64038 (Check impl trait substs when checking for recursive types) - #64043 (Add some more tests for underscore imports) - #64092 (Update xLTO compatibility table in rustc book.) - #64110 (Refer to "`self` type" instead of "receiver type") - #64120 (Move path parsing earlier) - #64123 (Added warning around code with reference to uninit bytes) - #64128 (unused_parens: account for or-patterns and `&(mut x)`) - #64141 (Minimize uses of `LocalInternedString`) - #64142 (Fix doc links in `std::cmp` module) - #64148 (fix a few typos in comments) Failed merges: r? @ghost
☔ The latest upstream changes (presumably #64160) made this pull request unmergeable. Please resolve the merge conflicts. |
Bot error? |
Yeah, there's been an uptick in that recently, not sure why. Should be all good though. |
(FWIW, the PR title is wrong now, it should mention 1.39.0.) |
Looks like it has already found some use in projects.
Resolves #58402.