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

Developers have their top System.Linq feature requests implemented #47231

Closed
6 tasks done
Tracked by #44314
eiriktsarpalis opened this issue Jan 20, 2021 · 6 comments
Closed
6 tasks done
Tracked by #44314
Assignees
Labels
area-System.Linq Bottom Up Work Not part of a theme, epic, or user story breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. Cost:S Work that requires one engineer up to 1 week Priority:3 Work that is nice to have User Story A single user-facing feature. Can be grouped under an epic.
Milestone

Comments

@eiriktsarpalis
Copy link
Member

eiriktsarpalis commented Jan 20, 2021

Creating this issue to keep track of System.Linq community feature requests that we are considering for .NET 6.

Done

Notes on Potential Breaking Changes

The changes add new method overloads to the System.Linq.Queryable APIs. This is known to break query provider implementations whose reflection code isn't sufficiently strong when looking up methods (cf. dotnet/efcore#24002, #49683). Query provider library authors are advised to ensure that their reflection code is tolerant of future method overload additions, e.g. by using a Type.GetMethod() overload that explicitly accepts the method's parameter types.

@eiriktsarpalis eiriktsarpalis added area-System.Linq User Story A single user-facing feature. Can be grouped under an epic. Priority:3 Work that is nice to have labels Jan 20, 2021
@eiriktsarpalis eiriktsarpalis added this to the 6.0.0 milestone Jan 20, 2021
@eiriktsarpalis eiriktsarpalis self-assigned this Jan 20, 2021
@ghost
Copy link

ghost commented Jan 20, 2021

Tagging subscribers to this area: @eiriktsarpalis
See info in area-owners.md if you want to be subscribed.

Issue Details

Creating this issue to keep track of System.Linq community feature requests that we are considering for .NET 6.

Issue Status Assignee
Support more arities for Enumerable.Zip Implementation merged @huoyaoyuan
Add SingleOrDefault/FirstOrDefault/LastOrDefault overloads that allow specifying a default API approved @Foxtrek64
Add an Enumerable.Partition method Ready for review
Add an Enumerable.ChunkBy method Ready for review
Add a non-enumerating Count method Ready for review
LINQ APIs to enable C# 8.0 index and range for IEnumerable API needs work
Add Enumerable.*By operators (DistinctBy, ExceptBy, IntersectBy, UnionBy, MinBy, MaxBy) API needs work
Author: eiriktsarpalis
Assignees: eiriktsarpalis
Labels:

Priority:3, User Story, area-System.Linq

Milestone: 6.0.0

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Jan 20, 2021
@eiriktsarpalis eiriktsarpalis added Cost:S Work that requires one engineer up to 1 week and removed untriaged New issue has not been triaged by the area owner labels Jan 20, 2021
@eiriktsarpalis eiriktsarpalis changed the title [System.Linq] .NET 6 Community API proposals Developers have their top System.Linq feature requests implemented Jan 20, 2021
@eiriktsarpalis eiriktsarpalis added the Bottom Up Work Not part of a theme, epic, or user story label Jan 20, 2021
@jeffhandley jeffhandley self-assigned this Jan 20, 2021
@MgSam
Copy link

MgSam commented Jan 21, 2021

Finally! After 14 years LINQ will finally get some attention again!

@GSPP
Copy link

GSPP commented Jan 28, 2021

This is very important work. The introduction of LINQ was such a boon to productivity on .NET. We were leading the entire industry. Now, some additional innovation is desirable to convert the experiences of a decade into widely useful data-processing methods.

@eiriktsarpalis
Copy link
Member Author

eiriktsarpalis commented Apr 9, 2021

All implementation PRs are now merged. Note that some of the new APIs are pending xml documentation, which I'll be introducing in tandem with work for #48986. cc @carlossanlop

@Thaina
Copy link

Thaina commented Apr 10, 2021

Sadly this not include #28650

@davidfowl
Copy link
Member

@eiriktsarpalis we need to make sure these go into the blog

eiriktsarpalis added a commit to eiriktsarpalis/runtime that referenced this issue Apr 21, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-System.Linq Bottom Up Work Not part of a theme, epic, or user story breaking-change Issue or PR that represents a breaking API or functional change over a prerelease. Cost:S Work that requires one engineer up to 1 week Priority:3 Work that is nice to have User Story A single user-facing feature. Can be grouped under an epic.
Projects
None yet
Development

No branches or pull requests

6 participants