Joseph Musser

@Joe4evr I don't think that comment is necessarily apropos.

@TahirAhmadov That name, though

That's an existing question that applies to assignments of properties. I would be very confused if the syntax did not desugar to a series of statements in the order that...

> While my scenario isn't about events, I recently encountered a case where the lack of compound assignment in with expressions sent me down an "expression-body-to-statement avalanche". This has happened...

`Click += new EventHandler(this.btn_Click) + new EventHandler(this.anyControl_Click)` would probably fall out automatically.

https://github.com/dotnet/roslyn/issues/11159#issue-153598385: > Limitations: > > * Events not permitted (at first)

> But one of the side-effects is that unlike tuples of two or more elements, you can't name that single element. I consider this a feature though. 😆

> I doubt there will be a non-generic IAsyncEnumerable, because it's not worth the effort. But let's assume we're willing to put any amount of effort into it. What would...

If there is no result being produced for each MoveNext, why would anyone want to call `MoveNextAsync` in a loop until it returns false versus just awaiting a non-generic `Task`?

Source generators are making this more painful. Mentioned in https://github.com/dotnet/roslyn/issues/44929 and a community member was asking about it on Gitter.