This is a tracking issue for the RFC "2996" (rust-lang/rfcs#2996).
The feature gate for the issue is #![feature(async_iterator)]
.
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.
Stream
and Iterator
Add core::stream::Stream
#79023 (comment)
Iterator
, clarifying panic behavior. The panic behavior between Stream
and Iterator
should be consistent.Stream::next
. This was removed from the RFC because it prevents dynamic dispatch, and subsequently removed from the implementation. This should be resolved before stabilizing.
fn poll_next
to async fn next
once we can use async
in traits.Iterator
and AsyncIterator
into a single trait which is generic over "asyncness".AsyncIterator
instead? Tracking Issue for #![feature(async_iterator)] #79024 (comment)schneiderfelipe, Berrysoft, bhgomes, mankinskin, waynexia and 51 morendelvalle, busyboredom, bhgomes, ahlinc, rushmorem and 4 moreTennyZhuang, luojia65, aykxt, ndelvalle, xiaoas and 10 more
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4