4 ms·
Not sure if I missed this in the post, does this depend on any unstabilized features or can we use this today on 1.10.0 stable? Awesome stuff btw, love the ite
by vvanders 10y ago
Not sure if I missed this in the post, does this depend on any unstabilized features or can we use this today on 1.10.0 stable?
Awesome stuff btw, love the iterator inspiration.
- pcwalton 10y agoI think "impl Trait" is unstable.
- steveklabnik 10y agoIt is, however, it's not currently actually using that syntax in the code: http://alexcrichton.com/futures-rs/futures/trait.Future.html http://alexcrichton.com/futures-rs/futures/trait.Future.html So, this will work on stable. It was presented that way to not get into the whole details about the whole impl trait shenanigans in general.
- pcwalton 10y agoAh, great news!
- eddyb 10y agoNot even in nightly yet - follow https://github.com/rust-lang/rust/pull/35091 https://github.com/rust-lang/rust/pull/35091 for updates (we're trying to land it this week).
- alexcrichton 10y agoYou can indeed use this on stable Rust today! Right now 1.9.0 is the minimum supported version due to the usage of `catch_panic` in a few places. I'd recommend a beta compiler for now though to compile some of the examples. There's a bug in the stable compiler which causes them to take up to 8x longer to compile, but beta/nightly are both speedy!
- vvanders 10y agoThat's so awesome. I was hoping that was the case. Serious Kudos, it feels like a lot of the promises of Rust are really paying off here.
- jdub 10y ago"promises" applause
- yoshuaw 10y agoHow do futures deal with panics? - should they even?
- aturon 10y agoPanics are caught at the "task" level -- and there's usually one task per connection. They don't take down the entire server (since tasks are isolation boundaries). Right now, nothing happens with the panic after it's caught, but we want to add hooks for doing something with it. Coming soon!