book-exploring-async-basics
book-exploring-async-basics copied to clipboard
cfsamson
The repository for the book "The Node Experiment - Exploring Async Basics with Rust"
Hello, I'm here again. > The next thing we need is a `Runtime` to hold all the state our `Runtime` needs. the first `Runtime` here is exactly a struct or...
> There are several ways to multitask. One is by progressing tasks concurrently, but not at the same time. Another is to progress two tasks at the exact same time...
> However, the part of Node that "progresses" your code does indeed run on a single thread. `progress` here is equal `interpret & compile`. So if there is a blocking...
> Poll our two event sources for new events `event sources` = `event queues`
> Now the parameter `_res` is an argument that is passed into our callback. In javascript it would be left out, but since we use a typed language we have...
> `Mio` powers the OS event queue used in [Tokio](https://github.com/tokio-rs/tokio), **which** is a runtime that provides I/O, networking, scheduling etc. Here the word `which` refers to `Tokio`, right? So does...
Hi, I'm Tae from Korea. This work is so informative thanks for sharing. If you don't mind, I'd like to translate it into Korean and share this broadly. Following #28,...
Hi, I am a developer from China. I found the book useful when I tried to figure out what eventloop is. Actually I'm still at the beginning part of this...
when you call `Runtime::run` you use the following code ```rust let rt_ptr: *mut Runtime = &mut self; unsafe { RUNTIME = rt_ptr }; ``` the code assumes that initialization of...
