We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
async for
for await
1 parent a82e5dd commit 17a273dCopy full SHA for 17a273d
text/0000-async_await.md
@@ -571,14 +571,14 @@ There are a couple of possible solutions:
571
This is left as an unresolved question to find another solution or decide which
572
of these is least bad.
573
574
-## `async for` and processing streams
+## `for await` and processing streams
575
576
Another extension left out of the RFC for now is the ability to process streams
577
-using a for loop. One could imagine a construct like `async for`, which takes
+using a for loop. One could imagine a construct like `for await`, which takes
578
an `IntoStream` instead of an `IntoIterator`:
579
580
```rust
581
-async for value in stream {
+for await value in stream {
582
println!("{}", value);
583
}
584
```
0 commit comments