Skip to content

Unstable (de facto internal) library feature gen_future links to a closed tracking issue (for async/await) #76249

Closed
@ArekPiekarz

Description

@ArekPiekarz
Contributor

Unstable Book in section gen_future leads to a closed tracking issue #50547 titled Tracking issue for async/await (RFC 2394).

There are a few solutions to this:
- reopen the tracking issue, or
- create a new tracking issue and a PR updating the issue number in documentation, or
- mark the feature as internal only, or
- something else?

Activity

added
A-docsArea: Documentation for any part of the project, including the compiler, standard library, and tools
on Oct 20, 2020
added
T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
C-bugCategory: This is a bug.
T-libsRelevant to the library team, which will review and decide on the PR/issue.
and removed
T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
on Feb 11, 2025
changed the title [-]Unstable Book: "gen_future" leads to a closed tracking issue[/-] [+]Unstable library feature `gen_future` links to a closed tracking issue (for async/await)[/+] on Feb 11, 2025
added
E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
on Feb 11, 2025
changed the title [-]Unstable library feature `gen_future` links to a closed tracking issue (for async/await)[/-] [+]Unstable (de facto internal) library feature `gen_future` links to a closed tracking issue (for async/await)[/+] on Feb 11, 2025
fmease

fmease commented on Feb 11, 2025

@fmease
Member

This is a de facto internal library feature that gates the internal ResumeTy & get_context used in the desugaring of async blocks as far as I can tell.

The solution is easy, simply replace the four occurrences of issue = "50547" in library/core/src/future/mod.rs with issue = "none". This way, the Unstable Book will automatically switch to the synopsis “This feature has no tracking issue, and is therefore likely internal to the compiler, not being intended for general use.”.

progressive-galib

progressive-galib commented on Feb 15, 2025

@progressive-galib
Contributor

@fmease done

progressive-galib

progressive-galib commented on Feb 15, 2025

@progressive-galib
Contributor

@rustbot claim

added a commit that references this issue on Feb 24, 2025

Rollup merge of rust-lang#137061 - progressive-galib:gen_future-closi…

b7f11ef

7 remaining items

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

Metadata

Metadata

Labels

A-async-awaitArea: Async & AwaitA-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsC-bugCategory: This is a bug.E-easyCall for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.T-libsRelevant to the library team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

    Development

    No branches or pull requests

      Participants

      @ArekPiekarz@fmease@camelid@rustbot@progressive-galib

      Issue actions

        Unstable (de facto internal) library feature `gen_future` links to a closed tracking issue (for async/await) · Issue #76249 · rust-lang/rust