This is a tracking issue for a for await loop variant that makes it easier to work with async iterators (#79024).
The feature gate for the issue is #![feature(async_for_loop)].
About tracking issues
Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
[ ] Get consensus on design, and if we even want this feature
The design for AsyncIterator still doesn't have consensus, and naturally the desugaring of for await will depend on this. Fortunately, the desugaring is an implementation detail so we aren't necessarily blocked on experimentation by that design.
Unresolved Questions
This is an early experimental feature, so basically every question is still unresolved.
eholk
commented
11 months ago
This is a tracking issue for a
for awaitloop variant that makes it easier to work with async iterators (#79024). The feature gate for the issue is#![feature(async_for_loop)].About tracking issues
Tracking issues are used to record the overall progress of implementation. They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions. A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Steps
Dependencies
79024
AsyncIteratorstill doesn't have consensus, and naturally the desugaring offor awaitwill depend on this. Fortunately, the desugaring is an implementation detail so we aren't necessarily blocked on experimentation by that design.Unresolved Questions
This is an early experimental feature, so basically every question is still unresolved.
Implementation history
118847