3 ms·
I believe the idea is that tokio, because of its zero-cost abstractions will be able to be efficiently be the foundation of those styles. Check out https://git
by tupshin 10y ago
I believe the idea is that tokio, because of its zero-cost abstractions will be able to be efficiently be the foundation of those styles.
Check out https://github.com/dpc/tokio-fiber/ https://github.com/dpc/tokio-fiber/ for co-routines being re-envisioned on tokio, and https://github.com/rust-lang/rfcs/issues/613 https://github.com/rust-lang/rfcs/issues/613 acknowledges that the actor story is still a work-in-progress.
I have seen no indication that either coroutines or futures will be less ergonomic or performant due to being built on top of tokio's futures.
- bsaul 10y agoThis whole discussion regarding concurrency/parallelism stacks made me think that there's probably a good blog post to write: Start with low-level OS system calls and show what pieces one needs to write to reach higher level abstractions like futures, coroutines , async / await, nodejs style event loop, or full blown actors. That would also make for a nice roadmap to whoever would like to build OTP or Akka style framework in Rust.