Closed
Description
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?
Metadata
Metadata
Assignees
Labels
Area: Async & AwaitArea: Documentation for any part of the project, including the compiler, standard library, and toolsCategory: This is a bug.Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.Relevant to the library team, which will review and decide on the PR/issue.
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
[-]Unstable Book: "gen_future" leads to a closed tracking issue[/-][+]Unstable library feature `gen_future` links to a closed tracking issue (for async/await)[/+][-]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)[/+]fmease commentedon Feb 11, 2025
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"
inlibrary/core/src/future/mod.rs
withissue = "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.”.gen_future
Feature Tracking #137061progressive-galib commentedon Feb 15, 2025
@fmease done
progressive-galib commentedon Feb 15, 2025
@rustbot claim
Rollup merge of rust-lang#137061 - progressive-galib:gen_future-closi…
7 remaining items