Heh, just realized we could get rid of the futures::ready macro if Poll implemented Try. Works perfectly as it's also an "unwrap or return" pattern. Not sure if it would confusing to some, but then again it's exactly why Try exists. And I use futures::ready! a *lot*.
-
-
Oh though if Try was implemented for `Result<Poll<T>>` that'd remove 50% of the futures::ready! calls in the codebase I'm working on.
Show this threadThanks. 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.
specializations