The code that I was able to rewrite from combinators to `async`/`await!` is certainly cool... But the need to pass a `Context` argument to absolutely everywhere I couldn't rewrite makes me want to re-open that can of worms...
-
Show this thread
-
In the majority of functions in hyper that would need to be passed a `Context`, none actually need to use it, they just need to pass it on the leaves. It just becomes noise.
1 reply 0 retweets 1 likeShow this thread -
Like, what if we need to pass around `Thread` from `main`, instead of being able to call `thread::current()`? That'd be horrible.
3 replies 1 retweet 7 likesShow this thread
It seems unfortunate to use revised `Future`/`Stream`/`AsyncRead` etc traits where the task is in TLS, but passing around the `Context` everywhere is just bad enough...
6:31 PM - 18 Sep 2018
0 replies
0 retweets
0 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.