Resolve overload ambiguities from lambda expression inference change

[cston]

Resolve overload ambiguities resulting from C#10 compiler changes to inference with lambda expressions.

See #58873 (comment)

cc @stephentoub

[ghost]

Tagging subscribers to this area: @tarekgh, @dotnet/area-system-linq-parallel
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Resolve overload ambiguities resulting from C#10 compiler changes to inference with lambda expressions.

See #58873 (comment)

cc @stephentoub

Author:	cston
Assignees:	-
Labels:	area-System.Linq.Parallel
Milestone:	-

[cston]

cc @ericstj, @ViktorHofer

[CyrusNajmabadi]

I would prefer we not take this, and we first see what we can do in the language to make these retain their original meaning.

[AlekseyTs]

Resolve overload ambiguities resulting from C#10 compiler changes to inference with lambda expressions.

Is there a spec or description of how the ambiguities are supposed to be resolved?

[cston]

I would prefer we not take this, and we first see what we can do in the language to make these retain their original meaning.

We can revert this change later if the C# compiler is updated to no longer report these cases as ambiguous. In the meantime, this change, or something similar, is needed to allow moving to the latest compiler.

[stephentoub]

In the meantime, this change, or something similar, is needed to allow moving to the latest compiler.

The test changes themselves look fine.

[ericstj]

agree with @cston, halting codeflow is bad as it allows changes to accumulate. I've been waiting on arcade flow since Monday (due to an assortment of issues), let's please get it unblocked. File an issue, with a nice repro and use this as a test case for that fix.