News for hackers. Stuff that matters.
Re:Making the Tokio scheduler 10x faster by carllerche on Monday October 14, 2019 @01:59PM (#21250980)
Ah, all the helpers around the "FSM" aspect of things are already exposed as part of the `futures` crate: https://github.com/rust-lang-nursery/futures-rs/
Re:Making the Tokio scheduler 10x faster by MuffinFlavored on Monday October 14, 2019 @07:34PM (#21254028)
Which is different than the standard adopted `std::futures`?
Re:Making the Tokio scheduler 10x faster by steveklabnik on Monday October 14, 2019 @08:44PM (#21254464)
No; it re-exports the standard futures. Its purpose is two-fold: one, it's where futures were experimented with before they got into std, and two, it's where extra functionality can live. We only put what was absolutely necessary into std.
Re:Making the Tokio scheduler 10x faster by shepmaster on Monday October 14, 2019 @08:42PM (#21254456)
Not quite. The futures crate, version 0.1, contained a definition of the `Future` trait and a bunch of the combinator methods. This was iterated on a lot. Eventually, the bare minimum traits were added to the standard library.

The futures crate, version 0.3 (released under the name `futures-preview` right now with an alpha version number), contains the helper methods for the standard library's trait.

Re:Making the Tokio scheduler 10x faster by autumnal on Tuesday October 15, 2019 @08:01AM (#21257569)
Just the bare minimum traits required for built-in async/.await, right?