4 ms·
I haven’t really seen any issues with async affecting other parts of Rust. People are successfully building systems applications, including game engines, crypto
by Ar-Curunir 3y ago
I haven’t really seen any issues with async affecting other parts of Rust. People are successfully building systems applications, including game engines, cryptography libraries, kernels, command line tools, compilers, etc, all without having to touch async.
I maintain large cryptography libraries, and have been completely unaffected by the async business.
- cmrdporcupine 3y agoI gripe about it all the time, but it hasn't really been an issue for me, and TBH the biggest codebase that I've written outside of work (where we don't really use async) ... uses tokio. I think it's more a question of emphasis. If you go looking for crates for network I/O related things (esp HTTP) on the whole you'll find mostly async driven ones. And among them, you'll often find they're hardcoded for tokio, too.