From 8dfd7f445c92deba74320a21fff957071451161b Mon Sep 17 00:00:00 2001 From: Carl Fredrik Samson Date: Sat, 5 Dec 2020 22:11:41 +0100 Subject: [PATCH] updated links to fix #21 --- README.md | 10 ++++++---- src/conclusion.md | 6 +++--- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index 1550ef3..7290c13 100644 --- a/README.md +++ b/README.md @@ -27,11 +27,13 @@ articles about async runtimes and executors, and if the rumors are right there is more to come from him in the near future. The way you should go about it is to read this book first, then continue -reading the [articles from stejpang](https://stjepang.github.io/) to learn more +reading the [articles from stejpang](https://web.archive.org/web/20200610130514/https://stjepang.github.io/) to learn more about runtimes and how they work, especially: -1. [Build your own block_on()](https://stjepang.github.io/2020/01/25/build-your-own-block-on.html) -2. [Build your own executor](https://stjepang.github.io/2020/01/31/build-your-own-executor.html) +1. [Build your own block_on()](https://web.archive.org/web/20200511234503/https://stjepang.github.io/2020/01/25/build-your-own-block-on.html) +2. [Build your own executor](https://web.archive.org/web/20200207092849/https://stjepang.github.io/2020/01/31/build-your-own-executor.html) + +> Sorry for the archive links. The original site doesn't exist anymore. ## Contributing @@ -45,7 +47,7 @@ Feedback, questions or discussion is welcome in the issue tracker. **2020-04-06:** Final draft finished -**2020-04-10:** Rather substantial rewrite of the `Reactor` to better the +**2020-04-10:** Rather substantial rewrite of the `Reactor` to better the readability and make it easier to reason about. In addition I fixed a mistake in the `Poll` method and a possible race condition. See #2 for more details. diff --git a/src/conclusion.md b/src/conclusion.md index 39dd40f..942ce5a 100644 --- a/src/conclusion.md +++ b/src/conclusion.md @@ -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