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!
-
-
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!
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.