-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Stabilize noop_waker #133089
Stabilize noop_waker #133089
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
5f259ac
to
55041d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Stabilizing this seems reasonable to me! We spent an extended period discussing this in @rust-lang/wg-async triage earlier this year, and I believe we were generally in favor of moving forward with this API. Thank you for putting this up!
@rfcbot fcp merge |
Team member @Amanieu 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 latest upstream changes (presumably #133349) made this pull request unmergeable. Please resolve the merge conflicts. |
Stabilize noop_waker Tracking Issue: rust-lang#98286 This is a handy feature that's been used widely in tests and example async code and it'd be nice to make it available to users. cc `@rust-lang/wg-async`
The job Click to see the possible cause of the failure (guessed by this bot)
|
💔 Test failed - checks-actions |
@bors retry This PR is having an unfortunate go of it. |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8dc8377): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 1.5%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 770.082s -> 769.893s (-0.02%) |
This also spuriously failed on msvc after it failed mingw |
This was accidentally reintroduced while editing rust-lang#133089.
…tolnay Remove rustc_const_stable attribute on const NOOP This was accidentally reintroduced while editing rust-lang#133089. r? dtolnay
…tolnay Remove rustc_const_stable attribute on const NOOP This was accidentally reintroduced while editing rust-lang#133089. r? dtolnay
Rollup merge of rust-lang#134100 - eholk:noop-rustc-const-stable, r=dtolnay Remove rustc_const_stable attribute on const NOOP This was accidentally reintroduced while editing rust-lang#133089. r? dtolnay
Tracking Issue: #98286
This is a handy feature that's been used widely in tests and example async code and it'd be nice to make it available to users.
cc @rust-lang/wg-async