public-collect/books-futures-explained
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

reworded paragraph re #36

Browse Source
This commit is contained in:
Carl Fredrik Samson
2021-01-15 16:18:56 +01:00
parent 2889b9d9a4
commit 800e923824
1 changed files with 2 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
src/1_futures_in_rust.md
View File

@@ -77,11 +77,8 @@ The key to these tasks is that they're able to yield control to the runtime's
scheduler and then resume execution again where it left off at a later point.
In contrast to leaf futures, these kind of futures do not themselves represent
an I/O resource. When we poll these futures they will run until they get to a
leaf function that blocks, where it yields control to the scheduler and waits
for some resource to signal us that it's ready so we can resume where we left
off. These futures can nest many non-leaf futures and will keep on going until
they get to a leaf-future which returns `Pending` when polled.
an I/O resource. When we poll them they will run until they get to a
leaf-future which returns `Pending` and then yield control to the scheduler.
## Runtimes