-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Comments
Tagging subscribers to this area: @eiriktsarpalis Issue DetailsCreating this issue to keep track of System.Linq community feature requests that we are considering for .NET 6.
|
Finally! After 14 years LINQ will finally get some attention again! |
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. |
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 |
Sadly this not include #28650 |
@eiriktsarpalis we need to make sure these go into the blog |
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 aType.GetMethod()
overload that explicitly accepts the method's parameter types.The text was updated successfully, but these errors were encountered: