3 ms·
> should be resolved ASAP I'm not sure having multiple runtimes is such a problem. The Rust async IO model was explicitly designed to accommodate different run
by oconnor663 7y ago
> should be resolved ASAP
I'm not sure having multiple runtimes is such a problem. The Rust async IO model was explicitly designed to accommodate different runtimes. There are a lot of tradeoffs around how a runtime does multi-threading, for example, and embedded systems may also do their own thing. Tokio vs async-std might or might not make sense as a long term split, but I think it's too early to say.
- xiphias2 7y agoI think the main clash was not about runtime differences but about the interface incompatibility (futures.rs) There's a bug for it in Tokio, but it's low priority as far as I know. https://github.com/tokio-rs/tokio/issues/1297 https://github.com/tokio-rs/tokio/issues/1297
- steveklabnik 7y agoIt's not particularly low priority https://github.com/tokio-rs/tokio/pull/1744 https://github.com/tokio-rs/tokio/pull/1744 (See the last section in particular)
- xiphias2 7y agoOh, so there's a pull request that I didn't see, the bugs don't show that it's being worked on. I understand that there are lots of hard technical issues to be resolved, it's just the visibility of this pull request wasn't that good. Thanks for the answer! Very interesting thread.
- twic 7y agoThis is a great thread! Lots of different perspectives on a difficult technical problem, plus appearances from many of my favourite Rust characters: we've got Ralf telling everyone that only abstract machines exist, boats turning up halfway through to contradict everyone, and Douman dropping by to offer the unhelpful C++ perspective.
- Argorak 7y ago> I think the main clash was not about runtime differences but about the interface incompatibility (futures.rs) There is a huge amount of complaints just fundamentally about async-std's existence, though.