Are there many complaints that it's too internally complicated? I've only heard complaints about it's API being difficult to use
-
-
This Tweet is unavailable.
-
Replying to @withoutboats @sgrif
I think the problem with tokio / futures rather is that you need to understand at least a good chunk of its lower level semantics in order to use it correctly / properly / at all.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
This Tweet is unavailable.
-
Replying to @withoutboats @CryZe107
If you're writing a semi-complicated `poll` implementation, you end up having to think way to hard about the order in which you call poll on other things. If you return `NotReady` without super for sure calling `Poll` on the thing that gets woken up, your future never resolves.
1 reply 0 retweets 2 likes -
This Tweet is unavailable.
-
Replying to @withoutboats
In this case there is no combinator that maps to what I need.
1 reply 0 retweets 0 likes -
This Tweet is unavailable.
-
Replying to @withoutboats
Too long to fit in a tweet. I can send you the code in a bit. Some of the complexity is because I couldn't have a borrowed value in here, but not all of it.
1 reply 0 retweets 0 likes
But this is a future that replicates a lot of how tokio-service works
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.