-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Tracking Issue for feature future_poll_fn
#72302
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
Comments
This exists in futures-lite, and people use it. It seems worth having available in the standard library. The naming discussion doesn't seem likely to change, and all else being equal there's a history for the name Shall we stabilize this? @rfcbot merge |
Team member @joshtriplett 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. This will be merged soon. |
…iplett Stabilize `future_poll_fn` FCP is done: rust-lang/rust#72302 (comment) Closes #72302 r? `@joshtriplett` as you started FCP Signed-off-by: Yuki Okushi <jtitor@2k36.org>
There are some soundness issues with See IRLO for details, in particular this miscompilation bug. |
I am proposing to change the |
Uh oh!
There was an error while loading. Please reload this page.
The feature gate for the issue is
#![feature(future_poll_fn)]
.Steps
future_poll_fn
#99306)Unresolved Questions
future::from_fn
instead?Implementation history
Rename fromfuture::poll_fn
tofuture::from_fn
in Renamecore::future::poll_fn
tocore::future::from_fn
#76789The text was updated successfully, but these errors were encountered: