std: ensure that the deadline has passed in sleep_until#151494
Merged
rust-bors[bot] merged 1 commit intorust-lang:mainfrom Jan 23, 2026
Merged
std: ensure that the deadline has passed in sleep_until#151494rust-bors[bot] merged 1 commit intorust-lang:mainfrom
sleep_until#151494rust-bors[bot] merged 1 commit intorust-lang:mainfrom
Conversation
Collaborator
This comment has been minimized.
This comment has been minimized.
4a976c5 to
978c5f5
Compare
Member
|
The docs are incredibly clear that it will never wake before the deadline and that it may sleep longer, so this absolutely seems like the right thing to do. @bors r+ |
Contributor
rust-bors bot
pushed a commit
that referenced
this pull request
Jan 23, 2026
Rollup of 4 pull requests Successful merges: - #151450 (std: use `clock_nanosleep` for `sleep` where available) - #151494 (std: ensure that the deadline has passed in `sleep_until`) - #151498 (global.rs: improve readability of re-entrance section) - #151504 (Reorganizing tests/ui/issues 11 tests [3/N]) r? @ghost
rust-timer
added a commit
that referenced
this pull request
Jan 23, 2026
Rollup merge of #151494 - joboet:sleep_until_ensure_elapsed, r=jhpratt std: ensure that the deadline has passed in `sleep_until` The clock source used for `sleep` might not be the same as the one used for `Instant`, so the implementation of `sleep_until` may not assume that the `Instant` has elapsed. This is particularly relevant on Windows, where [`QueryPerformanceCounter`](https://learn.microsoft.com/en-us/windows/win32/api/profileapi/nf-profileapi-queryperformancecounter) is used for `Instant`, but [`SetWaitableTimer`](https://learn.microsoft.com/en-us/windows/win32/api/synchapi/nf-synchapi-setwaitabletimer) is (probably[^1]) based on [`QueryUnbiasedInterruptTimePrecise`](https://learn.microsoft.com/en-us/windows/win32/api/realtimeapiset/nf-realtimeapiset-queryunbiasedinterrupttimeprecise). If these clocks drift apart, the `sleep` might return before the deadline has passed. Thus, this PR makes `sleep_until` recheck the current time after waking up and restart the `sleep` if necessary. [^1]: The documentation doesn't specify a clock, but `QueryUnbiasedInterruptTimePrecise` uses the same units and doesn't count time during sleep either, so I'd wager it's what is used for the timer.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The clock source used for
sleepmight not be the same as the one used forInstant, so the implementation ofsleep_untilmay not assume that theInstanthas elapsed. This is particularly relevant on Windows, whereQueryPerformanceCounteris used forInstant, butSetWaitableTimeris (probably1) based onQueryUnbiasedInterruptTimePrecise. If these clocks drift apart, thesleepmight return before the deadline has passed.Thus, this PR makes
sleep_untilrecheck the current time after waking up and restart thesleepif necessary.Footnotes
The documentation doesn't specify a clock, but
QueryUnbiasedInterruptTimePreciseuses the same units and doesn't count time during sleep either, so I'd wager it's what is used for the timer. ↩