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.

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

[Proposal]: Better Conversion from Collection Expression (VS 17.12, .NET 9) #8374

Open
2 of 4 tasks
333fred opened this issue Aug 20, 2024 · 0 comments
Open
2 of 4 tasks
Assignees
Labels
Implemented Needs ECMA Spec This feature has been implemented in C#, but still needs to be merged into the ECMA specification Proposal champion
Milestone

Comments

@333fred
Copy link
Member

333fred commented Aug 20, 2024

Better conversion from collection expression

Summary

Updates to the better conversion rules to be more consistent with params, and better handle current ambiguity scenarios. For example, ReadOnlySpan<string> vs ReadOnlySpan<object> can currently cause ambiguities during overload resolution for [""]. This is an issue because .NET 9 is adding such methods to string.Concat, which we need to address in the language.

Design meetings

@jcouv jcouv added this to the Working Set milestone Sep 13, 2024
@jcouv jcouv added the Implemented Needs ECMA Spec This feature has been implemented in C#, but still needs to be merged into the ECMA specification label Sep 21, 2024
@jcouv jcouv changed the title [Proposal]: Better Conversion From Collection Expression [Proposal]: Better Conversion from Collection Expression (VS 17.12, .NET 9) Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Implemented Needs ECMA Spec This feature has been implemented in C#, but still needs to be merged into the ECMA specification Proposal champion
Projects
None yet
Development

No branches or pull requests

3 participants