But remember, the Future trait and the futures crate have always been intentionally designed to be completely agnostic to the underlying runtimes. So there shouldn't be any fragmentation, no matter how many runtimes there are. 3/15
Over time I've become somewhat of an "async skeptic". Threads are really not as expensive as is commonly thought. A lot of async code isn't async - it just does stuff on to the blocking pool. So really only networking is actually fast when async and worthwhile being async, IMO...
-
-
Yeah, I absolutely agree on that, performance with blocking pools is notably slower than `std::fs` ops on a current thread. I do love the idea of "async" keyword being a marker of the unpredictable execution time, though :)
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.