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

changed paragrapth as suggested in reddit comment

Browse Source
This commit is contained in:
Carl Fredrik Samson
2021-01-14 21:35:54 +01:00
parent d06e85aa46
commit 0b6ac51ec9
1 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/1_futures_in_rust.md
View File

@@ -77,9 +77,11 @@ 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. 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 In contrast to leaf futures, these kind of futures do not themselves represent
an I/O resource. When we poll these futures we either run some code or we yield an I/O resource. When we poll these futures we it will run until they get to a
to the scheduler while waiting for some resource to signal us that it's ready so leaf function that blocks, where it yields control to the scheduler and waits
we can resume where we left off. 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 and will keep
on going until they get to a leaf-future which returns `Pending` when polled.
## Runtimes ## Runtimes