Closed
Description
This is a tracking issue for #![feature(async_closure)] (rust-lang/rfcs#2394).
The feature gate provides the async |...| expr closure syntax.
As with all tracking issues for the language, please file anything unrelated to implementation history, that is: bugs and design questions, as separate issues as opposed to leaving comments here. The status of the feature should also be covered by the feature gate label. Please do not ask about developments here.
Steps:
- Implement the RFC
- Accept another RFC
- Implement it: Rework support for async closures; allow them to return futures that borrow from the closure's captures #120361
- Adjust documentation (see instructions on rustc-guide)
- Stabilization PR (see instructions on rustc-guide)
Open questions (RFC 2394)
- Interaction between signature deduction and new solver.
Open questions (RFC 3668)
- Which syntax should we choose for bounds?
Related
Metadata
Metadata
Assignees
Labels
Area: Async & Await`async || {}`Area: Closures (`|…| { … }`)Async-await issues that have been triaged during a working group meeting.Blocker: Approved by a merged RFC but not yet implemented.Blocker: Approved by a merged RFC and implemented but not stabilized.Blocker: Implemented in the nightly compiler and unstable.Category: An issue tracking the progress of sth. like the implementation of an RFCStatus: It's hard to tell what's been done and what hasn't! Someone should do some investigation.Relevant to the language team, which will review and decide on the PR/issue.Working group: Async & awaitThis issue requires a nightly compiler in some way.