-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[release/6.0] Fix Queryable-to-Enumerable overload mapping logic #65857
Conversation
Tagging subscribers to this area: @dotnet/area-system-linq Issue DetailsBackport of #65569 to release/6.0 /cc @eiriktsarpalis Customer ImpactTestingRiskIMPORTANT: If this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like a clean backport. LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM -- no need for package authoring as this only ships in framework.
Failure is fixed by #66366 |
Backport of #65569 to release/6.0
/cc @eiriktsarpalis
Customer Impact
Addresses a customer reported regression from .NET 5 (#65419). The inclusion of new
FirstOrDefault
/SingleOrDefault
/LastOrDefault
overloads in .NET 6 has surfaced a bug in our Queryable-to-Enumerable method mapping logic in System.Linq.Queryable.Testing
Added unit tests verifying that the regression no longer occurs.
Risk
Low to moderate. Updates the product code to account for the corner case introduced by the new overloads.