2 ms·
That hasn't been the case. In practice, mio is the standard for everything asynchronous in Rust. Adopting Go's approach would force either asynchronous I/O or
by pcwalton 11y ago
That hasn't been the case. In practice, mio is the standard for everything asynchronous in Rust.
Adopting Go's approach would force either asynchronous I/O or M:N threading on everyone, which is unacceptable for Rust's goals.