-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
System.Collections work planned for .NET 8 #77391
Comments
Tagging subscribers to this area: @dotnet/area-system-collections Issue DetailsThis issue captures the planned work for .NET 8. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope. SummaryFor .NET 8 we are prioritizing System.Collections work according to the following high-level themes:
Planned for .NET 8New APIsNovel or high-impact functionalityPerf oriented
Convenience APIs
Analyzers
Quality/reliability fixes
AOTWork done in previous releasesStill under consideration
|
@krwq, did you intend to close this? |
Yes, we started closing some user stories issues during our triage meeting and since there are only few things left it's easier to track them individually |
I'd like to leave this open. @ericstj and I use these meta issues for tracking:
@krwq From your comment, I infer that you and the rest of the @dotnet/area-system-collections crew has finished refining the backlog of issues in the 8.0.0 milestone and that you folks plan to track progress based on what's still open within the milestone; is that correct? |
@jeffhandley yes, we've went through all 8.0 issues in our areas and will be tracking with 8.0 issues and triage board. We generally left 8.0 milestones on things we're actively/potentially work on (including any regressions etc.). For some "maybe"/"unsure" issues given number of issues we currently have we also moved them to Future under assumption if there is strong enough feedback they will show up on our triage board and we can reconsider them again. On the way we've closed couple of issues like this one which on their own didn't describe the problem (except maybe title) but were tracking other issues and are not helping with any active/potential work in this release (since they will be outdated in next release). I don't think anyone will have any strong objections to to keep this one open but having said that it's not super useful from our perspective given we can find even more up to date list with |
Any chance of having #31001 (Have mutable collection interfaces implement read only interfaces) for NET8 ? While it would probably require some additional work in the runtime and type loader to make an (internal) solution for the typeloader (diamond dependency problem) so that any default interface implementations on the collection types have a lower priority than normal, it would make the built in readonly interfaces a lot more useful |
Closing as completed. |
This issue captures the planned work for .NET 8. This list is expected to change throughout the release cycle according to ongoing planning and discussions, with possible additions and subtractions to the scope.
Summary
For .NET 8 we are prioritizing System.Collections work according to the following high-level themes:
Planned for .NET 8
New APIs
Novel or high-impact functionality
Perf oriented
Convenience APIs
ImmutableArray<T>.Builder.ToImmutableAndClear()
#72625Analyzers
Quality/reliability fixes
Work done in previous releases
Moved to Future
The text was updated successfully, but these errors were encountered: