4 ms·
> why Rust and Python put so much effort into adding event loops after the fact. Perhaps Python, but Rust went the other way - it had all that stuff built and
by jen20 5mo ago
> why Rust and Python put so much effort into adding event loops after the fact.
Perhaps Python, but Rust went the other way - it had all that stuff built and it was removed.
- traderj0e 5mo agoEr yeah technically the event loop isn't part of Rust, just the async/await syntax. But it's implied that you're going to use some event loop with it.
- tracker1 5mo agoNo, it's implied that you're going to use some sort of async runtime with it... said runtime can be simple real threads, a thread pool or virtual threads and there are implementations for all of them. And even then, it's super easy to start a new real thread in rust, around any async runtime.
- jen20 5mo agoWhile true, this isn’t what I’m talking about: Rust had _built in_ green threads at one point, the same as Go [1]. [1]: https://rust-lang.github.io/rfcs/0230-remove-runtime.html https://rust-lang.github.io/rfcs/0230-remove-runtime.html
- jen20 5mo agoTrue now, but there was a time when async/await was _not_ part of Rust, and a runtime was.