Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Overload resolution ambiguity introduced by SDK 8.0.300-preview.24203.14 #40235

Closed
danielcweber opened this issue Apr 17, 2024 · 1 comment
Closed

Overload resolution ambiguity introduced by SDK 8.0.300-preview.24203.14 #40235

danielcweber opened this issue Apr 17, 2024 · 1 comment
Assignees
@dsplaisted
Labels
untriaged Request triage from a team member

Comments

@danielcweber
Copy link

danielcweber commented Apr 17, 2024 •
edited
Loading

The SDK 8 preview that comes with the latest VS2022 preview introduces an overload resolution ambiguity that is not in the stable SDK. See this repo for a reproduction and this or this workflow run to watch a build fail.

The issue is also in the latest SDK 9 preview. It's not reproducible on dotnetfiddle, the latest SDK bits there are from Jan 24.

Everything is fine on 8.0.204.

This might be related to collection expression conversions since the method overload in question has a params [] parameter.
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Apr 17, 2024
@dotnet-issue-labeler dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@danielcweber danielcweber mentioned this issue May 6, 2024
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees

@dsplaisted dsplaisted

Labels
untriaged Request triage from a team member
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@dsplaisted @danielcweber