Skip to content

Tracking Issue for core::task::ready! macro #70922

Closed

Description

@yoshuawuyts

This is a tracking issue for the ready! macro.
The feature gate for the issue is #![feature(ready_macro)].

Steps / History

Unresolved Questions

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Apr 8, 2020
  2. added
    A-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)
    B-unstableBlocker: Implemented in the nightly compiler and unstable.
    T-libs-api[DEPRECATED; DO NOT USE]
    on Apr 8, 2020
  3. changed the title [-]Tracking Issue for ready! macro[/-] [+]Tracking Issue for core::task::ready! macro[/+] on Jul 15, 2020
  4. added a commit that references this issue on Jul 18, 2020
  5. added
    Libs-SmallLibs issues that are considered "small" or self-contained
    I-libs-radarLibs issues that are tracked on the team's radar.
    on Jul 29, 2020
  6. added
    AsyncAwait-TriagedAsync-await issues that have been triaged during a working group meeting.
    on Aug 4, 2020
  7. yoshuawuyts commented on Nov 19, 2020

    @yoshuawuyts
    MemberAuthor

    #77862 seems like it may resolve the rustdoc issue

  8. RalfJung commented on Nov 22, 2020

    @RalfJung
  9. yoshuawuyts commented on Nov 22, 2020

    @yoshuawuyts
    Author
  10. yoshuawuyts commented on Jul 30, 2021

    @yoshuawuyts
    MemberAuthor

    Closed via #81050

  11. 3 remaining items

  12. rfcbot commented on Jul 6, 2022

    @rfcbot

    Team member @m-ou-se 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.

  13. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    and removed
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Jul 6, 2022
  14. rfcbot commented on Jul 6, 2022

    @rfcbot

    🔔 This is now entering its final comment period, as per the review above. 🔔

  15. added
    to-announceAnnounce this issue on triage meeting
    and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Jul 16, 2022
  16. rfcbot commented on Jul 16, 2022

    @rfcbot

    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.

  17. added 2 commits that reference this issue on Jul 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-async-awaitArea: Async & AwaitA-macrosArea: All kinds of macros (custom derive, macro_rules!, proc macros, ..)AsyncAwait-TriagedAsync-await issues that have been triaged during a working group meeting.B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCI-libs-radarLibs issues that are tracked on the team's radar.Libs-SmallLibs issues that are considered "small" or self-containedT-libs-api[DEPRECATED; DO NOT USE]disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions