So writing manual Futures while not requiring Unpin is anti-fun. Truly considering that hyper std::future support releases with Rust 1.37 (async/await), not with 1.36...
Instead of exporting a type that implements Future and manually verifying the unsafe pin usage, just export an `async fn`. It's not nameable, but should be safer
-
-
I think it makes sense to play to the language's strengths by doing things in a way that will let the typechecker do the checking, instead of trying to do the checking manually. Shipping something 6 weeks faster would seem like a bad decision 6 weeks later.
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.