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
I'm a bit confused that there seems to be some opposition to the RFC, but I'm not deep in enough to understand quickly.
1 reply 0 retweets 0 likes -
Replying to @Argorak
This patch on Waker, or the Following stabilization RFC?
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @Argorak
Argh, autocomplete. *Futures stabilization.
1 reply 0 retweets 0 likes -
Replying to @Argorak @yoshuawuyts
The opposition wants to split Waker into Waker and LocalWaker. In single-threaded executors, it'd make some optimizations easier (and enable some really minor ones), while the API would be more complex. But it's a niche use case so we figured it's not worth it. costs > benefits
12:31 PM - 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.