Some musings on the async ecosystem and compatibility between async-std and tokio... 1/15
-
-
Go doesn't need to worry as much because it's primarily designed for servers, so it can have one runtime. But people want to use Rust everywhere. Environments on which async-std and tokio can compile and run well, and ones at which Rust excels are just a small part of that.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Firecracker is more of an example of dumping async/await entirely. Futures already largely determine how the executor has to function and if you want interoperability it will be even harder to apply to situations where people might want a custom executor.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.