Tagging subscribers to this area: @dotnet/area-system-io
See info inarea-owners.md if you want to be subscribed.

the failures are unrelated, I am merging

I wish our compiler could optimize that for us.

For the most part this is by design: to maintain order of operations, if you haveA() + await B() the compiler has to evaluateA() first, at which point it has to store the result somewhere across the await. In this constrained case, whereA() is actually a local whose address is never exposed, isn't passed by ref, isn't captured by a closure, etc., it could probably avoid it, and for that I openeddotnet/roslyn#54629. But it's also possible the rewards from such a constrained optimization are limited (e.g. these were the only two occurrences in product code of+ await in all of dotnet/runtime), and there may be reasons why even for this case the compiler might face correctness issues.

@stephentoub thanks!