6

Tracking Issue for feature `future_poll_fn` · Issue #72302 · rust-lang/rust · Gi...

 2 years ago
source link: https://github.com/rust-lang/rust/issues/72302
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
neoserver,ios ssh client

Tracking Issue for feature future_poll_fn #72302

2 tasks

yoshuawuyts opened this issue on May 17, 2020 · 3 comments

2 tasks

Comments

Member

yoshuawuyts commented on May 17, 2020

edited by JohnTitor

The feature gate for the issue is #![feature(future_poll_fn)].

Steps

Unresolved Questions

  • Should this be named future::from_fn instead?

Implementation history

  • Initial implementation in #72303
  • Rename from future::poll_fn to future::from_fn in #76789
    • closed as it's ambiguous, see the discussion on that PR

yoshuawuyts

added the C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. label

on May 17, 2020

jonas-schievink

added A-async-await Area: Async & Await B-unstable Implemented in the nightly compiler and unstable. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

labels

on May 17, 2020

tmandry

added the AsyncAwait-Triaged Async-await issues that have been triaged during a working group meeting. label

on May 19, 2020

KodrAus

added the Libs-Tracked Libs issues that are tracked on the team's project board. label

on Jul 29, 2020

Member

joshtriplett commented 18 days ago

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 poll_fn.

Shall we stabilize this?

@rfcbot merge

rfcbot commented 18 days ago

edited by BurntSushi

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.

rfcbot

added proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it.

labels

18 days ago

rfcbot

added the final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. label

8 days ago

rfcbot commented 8 days ago

bellThis is now entering its final comment period, as per the review above. bell

yoshuawuyts reacted with hooray emoji All reactions

rfcbot

removed the proposed-final-comment-period Proposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off. label

8 days ago

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Assignees

No one assigned

Labels
A-async-await Area: Async & Await AsyncAwait-Triaged Async-await issues that have been triaged during a working group meeting. B-unstable Implemented in the nightly compiler and unstable. C-tracking-issue Category: A tracking issue for an RFC or an unstable feature. disposition-merge This issue / PR is in PFCP or FCP with a disposition to merge it. final-comment-period In the final comment period and will be merged soon unless new substantive objections are raised. Libs-Tracked Libs issues that are tracked on the team's project board. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects

None yet

Milestone

No milestone

Development

No branches or pull requests

6 participants

About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK