-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify docs regarding sleep of zero duration #79849
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @sfackler (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
98a27d9
to
c40b5ca
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
|
9170082
to
d0774a5
Compare
@Digital-Chaos I'm not the right reviewer, I'm not on the libs team. |
We've discussed this PR in the library team meeting a few days ago, and felt like an overview of what happens on the different platforms just like for |
Thanks for the feedback! As we are going for the extra docs route, will the change in his PR suffice or do we need more detail? |
Ah sorry; to clarify: We don't want to promise anything here, so something like
should not be there. That information would be fine if it was clear this is not a promise, but just a description of the current implementation. So, something like "Currently, .." or "The current implementation ...". See the documentation of Also, just like I'd say linking |
The job Click to see the possible cause of the failure (guessed by this bot)
|
Updated to specify the underlying syscalls
a57d79e
to
8a85a85
Compare
This comment has been minimized.
This comment has been minimized.
Fix link reference Co-authored-by: Joshua Nelson <[email protected]>
@Digital-Chaos any updates on changing this to match the meeting decision |
@Dylan-DPC, I updated the PR on 15th Jan with more info taking into account the feedback from @m-ou-se, and which was subsequently fixed by @jyn514 (also the 15th Jan), not quite sure why the status this PR is tagged as S-waiting-on-author? |
Ah ok, I didn't realize this was waiting on review. In the future you can use @rustbot modify labels: -S-waiting-on-author +S-waiting-on-review |
Thanks! @bors r+ rollup |
📌 Commit bb2a27b has been approved by |
Rollup of 11 pull requests Successful merges: - rust-lang#79849 (Clarify docs regarding sleep of zero duration) - rust-lang#80438 (Add `Box::into_inner`.) - rust-lang#81466 (Add suggest mut method for loop) - rust-lang#81687 (Make Vec::split_at_spare_mut public) - rust-lang#81904 (Bump stabilization version for const int methods) - rust-lang#81909 ([compiler/rustc_typeck/src/check/expr.rs] Remove unnecessary refs in pattern matching) - rust-lang#81910 (Use format string in bootstrap panic instead of a string directly) - rust-lang#81913 (Rename HIR UnOp variants) - rust-lang#81925 (Add long explanation for E0547) - rust-lang#81926 (add suggestion to use the `async_recursion` crate) - rust-lang#81951 (Update cargo) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Clarify that the behaviour of sleep() when given a duration of zero is actually platform specific.