-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Remove unstable Poll::ready
#107060
Remove unstable Poll::ready
#107060
Conversation
r? @scottmcm (rustbot has picked a reviewer for you, use r? to override) |
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
This comment has been minimized.
This comment has been minimized.
I believe this requires an ACP, so please create one (if you haven't already). @rustbot label T-libs-api -T-libs S-waiting-on-author -S-waiting-on-review |
@rustbot label -S-waiting-on-author S-waiting-on-ACP |
☔ The latest upstream changes (presumably #109732) made this pull request unmergeable. Please resolve the merge conflicts. |
ACP approved, r=me on the PR with the conflict removed. |
@bors delegate |
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
This comment was marked as duplicate.
@bors r=joshtriplett |
☀️ Test successful - checks-actions |
Finished benchmarking commit (8a281f9): 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)ResultsThis 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.
CyclesResultsThis 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: 640.817s -> 643.295s (0.39%) |
Based on the discussion in #89780, this API is problematic and would likely require changes over an edition. Now that
task::ready!
is stabilized, this seems unlikely to happen, so I think we should just go ahead and remove it.ACP: rust-lang/libs-team#214