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

updated

Browse Source
This commit is contained in:
Carl Fredrik Samson
2020-04-01 19:51:30 +02:00
parent 70c4020059
commit 5c10caf9c5
1 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/1_background_information.md
View File

@@ -4,7 +4,7 @@
> >
> - High level introduction to concurrency in Rust > - High level introduction to concurrency in Rust
> - Knowing what Rust provides and not when working with async code > - Knowing what Rust provides and not when working with async code
> - Understanding why we need runtimes > - Understanding why we need a runtime-library in Rust
> - Getting pointers to further reading on concurrency in general > - Getting pointers to further reading on concurrency in general
Before we start implementing our `Futures` , we'll go through some background Before we start implementing our `Futures` , we'll go through some background
@@ -13,6 +13,18 @@ information that will help demystify some of the concepts we encounter.
Actually, after going through these concepts, implementing futures will seem Actually, after going through these concepts, implementing futures will seem
pretty simple. I promise. pretty simple. I promise.
## Popular alternatives for writing concurrent programs
So let's kick this off by first taking a brief look into what the popular
options we have for writing concurrent programs
### Callback based approcah
You probably already know this from Javascript since it's extremely common:
## Futures ## Futures
So what is a future? So what is a future?