Just because the state of async I/O in Rust is not messy enough > “Romio is a fork of another Rust project called Tokio”https://github.com/withoutboats/romio …
-
-
Nim’s AsyncDispath module isn’t bad either. It’s similar to what Rust is painfully trying to build, but has been driven by the willingness to solve real, rather than conceptual problems. Swift has the same issues as Rust, btw. Async I/O shouldn’t be an afterthought.
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Rust started out with native M:N threading but it was counter to the goals of being a viable systems language. It needed 1:1 threading to able to compete on performance with C, interact well with other languages, etc. If it didn't make these choices, what would be the use case?
-
Rust is trying to be something much different from Go. Despite offering more fancy high-level language features, it's a lower-level language. It dropped features like M:N threading and garbage collection because they compromised viability in the main niche it was aiming to fill.
- 1 more reply
New conversation -
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.