Yessssss! The Waker simplification for Futures has been merged into the main RFC! -- https://github.com/aturon/rfcs/pull/16 … So no more LocalWaker / Waker distinction. Only 1 Waker type is needed to signal a Future is ready. This means we're *so close* to having Futures land on stable!
-
Show this thread
-
Replying to @yoshuawuyts
Looking at the final poll signature, it just feels so right and self-explanatory: fn poll(self: Pin<&mut Self>, waker: &Waker) -> Poll<Self::Output> We came a loooong way since fn poll(&mut self) -> Poll<Self::Item, Self::Error>
1 reply 1 retweet 11 likes
Replying to @stjepang
For people reading along: the old API also had Waker but accessed as global, had a task-local context as a global too, and could only ever return Result. There were important things missing in the function signature!
6:31 AM - 24 Jan 2019
0 replies
0 retweets
2 likes
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.