News for hackers. Stuff that matters.
Re:Rust async-await status report 2 by 0815test on Wednesday July 10, 2019 @01:07PM (#20403959)
The basic interfaces are built into the standard library, precisely in order to ensure compatibility across the Rust ecosystem. So if you're writing something that's compatible with the basic futures/async model, you'll be able to use any provided runtime with Rust. It may be possible to do even better in the future (use HKT to enable the exact same code to be compiled as either "sync" or "async"-based) but I'm not sure why you think that the previous model of making Rust into yet another heavy runtime-based language (with a handful of weird, tacked-on functional features that would not even help performance to any real extent given those prereqs, but still making the language even harder to grok than Haskell!) is preferable.
Re:Rust async-await status report 2 by pjmlp on Wednesday July 10, 2019 @01:30PM (#20404243)
The challenge is going to be the same that C++ had until ISO C++ finally understood the way forward was to actually have them in the standard.

A bunch of third party libraries with different levels of quality not guaranteed to be available across all target platforms supported by the language.