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);
A cool thing of requiring await is that it opens the natural path to add contextual control-flow keywords beyond await. E.g. // current let a = action_one(); let b = action_two(); try_join!(a, b)?; // proposed await? join { action_one(), action_two(), };
-
-
await join, await select, await race await? join, await? select, await? race Together filling out the matrix of {fallible,infallible} x {syn,async} control flow.
Thanks. 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.