I wonder if with keyword-await it would make sense for the futures concurrency macros to not await inside of them. It prob doesn't w macro await. E.g. // current try_join!(a, b)?; // await w/ macro await!(try_join(a, b))?; // await w/ keyword await? try_join(a, b);
-
Show this thread
-
(note: don't want to debate syntax) Just realized what was bothering me when I was writing my toy proxy server yest: `try_join` without `await` made it hard to figure out we're awaiting something. E.g. now we need to remember that `try_join` is a superset/alias of `await`.
1 reply 0 retweets 1 likeShow this thread
Probably need to flesh these ideas out in more detail at some point.
10:07 AM - 18 Mar 2019
0 replies
0 retweets
1 like
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.