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

Merge pull request #5 from olehmisar/patch-1

Browse Source 
Minor fixes of verbs
This commit is contained in:
Carl Fredrik Samson
2020-04-10 14:49:22 +02:00
committed by GitHub
parent 39aecb264a 331bf7e4df
commit 08cda06ade
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/1_futures_in_rust.md
View File

@@ -54,7 +54,7 @@ completion alone as you'll understand by reading the next paragraph.
### Non-leaf-futures ### Non-leaf-futures
Non-leaf-futures is the kind of futures we as _users_ of a runtime writes Non-leaf-futures is the kind of futures we as _users_ of a runtime write
ourselves using the `async` keyword to create a **task** which can be run on the ourselves using the `async` keyword to create a **task** which can be run on the
executor. executor.
@@ -112,7 +112,7 @@ notifying a `Future` that it can do more work, and actually doing the work
on the `Future`. on the `Future`.
You can think of the former as the reactor's job, and the latter as the You can think of the former as the reactor's job, and the latter as the
executors job. These two parts of a runtime interacts using the `Waker` type. executors job. These two parts of a runtime interact with each other using the `Waker` type.
The two most popular runtimes for `Futures` as of writing this is: The two most popular runtimes for `Futures` as of writing this is: