Fred Silberberg
Fred Silberberg
1. That's not about lambdas in general, it's about expression trees. And yes, expression trees need to reflect the code as written. 2. This would not be a language feature...
Closing as a duplicate of https://github.com/dotnet/csharplang/issues/3951.
> @333fred may want to take a peek at the OverloadResolutionPriority docs as well LGTM.
> Would it make sense to limit this to only primary constructor parameters? Yes, that is one of the points that the LDM has been actively debating. I don't recall...
Please keep discussion of readonly locals out of this issue. You can continue discussing that topic in https://github.com/dotnet/csharplang/discussions/8479.
It is expected that this does not yet compile. I wanted to get feedback on the approach before taking more time to go through and handle all the cases.
@jcouv @RikkiGibson this is ready for review. I'll likely have another commit sometime tomorrow that also adds runtime async verification for `await foreach` tests, but I don't anticipate that to...
> Was there anything in particular to observe here? This should not have been affected by the change in this PR, right? Correct, I'm verifying that fact.
> Do we understand what API we used for async that we no longer use for runtime-async? None. The non-runtime async code does not verify diagnostics, this is present on...
> nit: Thanks for pointing out this test. Consider leaving a comment for what to look for in the IL (this is an async test where the new "throw null"...