4 ms·
> as best I remember the history of Rust There's an RFC for that! https://github.com/rust-lang/rfcs/blob/master/text/0230-remove-runtime.md https://github.com/
by steveklabnik 10y ago
> as best I remember the history of Rust
There's an RFC for that! https://github.com/rust-lang/rfcs/blob/master/text/0230-remove-runtime.md https://github.com/rust-lang/rfcs/blob/master/text/0230-remo... (A reminder that this was written in 2014, so statements are about Rust at that time period)
> I think Rust will eventually move back in that direction
Note that tokio is not "green threads" as they're conventionally thought of, though they are similar if you squint, kinda.
- ekidd 10y ago> Note that tokio is not "green threads" as they're conventionally thought of, though they are similar if you squint, kinda. Well, I'm leaping ahead to the end of the story, here, and speaking far too loosely about technical details. ;-) Futures + tokio + a possible future async/await proposal would provide a reasonable enough syntax for actors/coroutines in Rust, I suspect.
- steveklabnik 10y agoFair enough! :) Relevant links: https://github.com/erickt/stateful https://github.com/erickt/stateful and https://github.com/rust-lang/rfcs/pull/1823 https://github.com/rust-lang/rfcs/pull/1823
- GolDDranks 10y agoFrom the author of the mioco coroutine library, there is a new attempt to implement coroutines on top of tokio: https://github.com/dpc/tokio-fiber/ https://github.com/dpc/tokio-fiber/ (still under construction, it seems)