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

updated links to fix #21

Browse Source
This commit is contained in:
Carl Fredrik Samson
2020-12-05 22:11:41 +01:00
parent 2128fc83d6
commit 8dfd7f445c
2 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/conclusion.md
View File

@@ -13,7 +13,7 @@ Until next time!
## Reader exercises
So our implementation has taken some obvious shortcuts and could use some improvement.
So our implementation has taken some obvious shortcuts and could use some improvement.
Actually digging into the code and try things yourself is a good way to learn. Here are
some good exercises if you want to explore more:
@@ -32,11 +32,11 @@ thing in a slightly different way to get some inspiration.
### Building a better exectuor
Right now, we can only run one and one future only. Most runtimes has a `spawn`
Right now, we can only run one and one future only. Most runtimes has a `spawn`
function which let's you start off a future and `await` it later so you
can run multiple futures concurrently.
As I suggested in the start of this book, visiting [@stjepan'sblog series about implementing your own executors](https://stjepang.github.io/2020/01/31/build-your-own-executor.html)
As I suggested in the start of this book, visiting [@stjepan'sblog series about implementing your own executors](https://web.archive.org/web/20200207092849/https://stjepang.github.io/2020/01/31/build-your-own-executor.html)
is the place I would start and take it from there.
### Create an unique Id for each task