2 ms·
> This quote from the article is incredibly sad: "each async library, comes its own ecosystem of libraries, which only work with that async library". Already i
by steveklabnik 6y ago
> This quote from the article is incredibly sad: "each async library, comes its own ecosystem of libraries, which only work with that async library".
Already in Rust many libraries can be written completely agnostic of the underyling executor. Some cannot; we have a bit more interface work to do, but there's nothing inherent about this, it's solely a standardization issue that's being worked on. Sounds like they ran into the latter more than the former, which is unfortunate, but should be better in the future.
> But is it actually _necessary_ to resort to async I/O in Rust, given that the type system appears to make thread-based concurrency safe ?
It is not!