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 …
-
-
Go goroutines and channels may suck and not appear to be “the best solution”, are not “zero abstraction” and are not “safe”. But they work. They are stable. They are easy to understand. They have been around forever. They are good enough for most real-world problems.
Show this thread -
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 thread
End of conversation
New conversation -
-
-
Per the README though, it looks to be a temporary stand-in utilizing the new async/await features that Tokio doesn’t yet have.
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.