Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

[Breaking change]: Ambiguous overload resolution #44102

Open
1 of 3 tasks
xtqqczze opened this issue Dec 28, 2024 · 0 comments
Open
1 of 3 tasks

[Breaking change]: Ambiguous overload resolution #44102

xtqqczze opened this issue Dec 28, 2024 · 0 comments
Assignees
@CamSoper
Labels
breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest. source incompatible Source code may encounter a breaking change in behavior when targeting the new version.

Comments

@xtqqczze
Copy link
Contributor

xtqqczze commented Dec 28, 2024 •
edited by sequestor bot
Loading

Description

Version

.NET 9

Previous behavior

no error

New behavior

(13,23): error CS0121: The call is ambiguous between the following methods or properties: 'Program.Join(string, params string[])' and 'Program.Join(string, params ReadOnlySpan<string>)'

Type of breaking change

  • Binary incompatible: Existing binaries might encounter a breaking change in behavior, such as failure to load or execute, and if so, require recompilation.
  • Source incompatible: When recompiled using the new SDK or component or to target the new runtime, existing source code might require source changes to compile successfully.
  • Behavioral change: Existing binaries might behave differently at run time.

Reason for change

Recommended action

Feature area

C#

Affected APIs

No response

Associated WorkItem - 360652
@xtqqczze xtqqczze added breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri1 High priority, do before Pri2 and Pri3 labels Dec 28, 2024
@dotnetrepoman dotnetrepoman bot added ⌚ Not Triaged Not triaged source incompatible Source code may encounter a breaking change in behavior when targeting the new version. labels Dec 28, 2024
@xtqqczze xtqqczze mentioned this issue Dec 28, 2024
Open
@CamSoper CamSoper removed the ⌚ Not Triaged Not triaged label Jan 7, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 7, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Jan 7, 2025
@CamSoper CamSoper added the 🗺️ reQUEST Triggers an issue to be imported into Quest. label Jan 7, 2025
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CamSoper CamSoper

Labels
breaking-change Indicates a .NET Core breaking change doc-idea Indicates issues that are suggestions for new topics [org][type][category] Pri1 High priority, do before Pri2 and Pri3 📌 seQUESTered Identifies that an issue has been imported into Quest. source incompatible Source code may encounter a breaking change in behavior when targeting the new version.
Projects
dotnet/docs January 2025 sprint project
Status: 🔖 Ready
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CamSoper @xtqqczze