-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Some usages of Contains no longer compile (optional argument in LINQ expression trees) #35547
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
Comments
This is a result of dotnet/runtime#110197, which adds an overload of MemoryExtensions.Contains that has an optional comparer parameter, but expression trees do not support optional parameters (in this repo we haven't yet updated to a version of the SDK which has this). I'll follow up on this in that issue. |
Because of the new .NET Contains overload with an optional parameter, which is incompatible with LINQ expression trees. See dotnet#35547
Because of the new .NET Contains overload with an optional parameter, which is incompatible with LINQ expression trees. See dotnet#35547
FYI I've submitted #35569 to temporary comment out the problematic tests and allow EF to build with the latest SDK - until we decide how to properly fix the situation. |
Because of the new .NET Contains overload with an optional parameter, which is incompatible with LINQ expression trees. See #35547
efcore
tests in VMR
Placing this in 10 as we'll need to find a solution to this (discussions are happening offline). |
Proposal to enable optional arguments in expression trees: dotnet/csharplang#9190. This would be the ideal fix for this. |
Fix to Roslyn to allow optional parameters in LINQ expression trees has been merged (thanks @cston). The next dotnet SDK update we get, we should be able to bring back the tests and close this. |
Here are the errors encountered when we tried to enable building tests in VMR:
For repro, add
/p:DotNetBuildTests=true
to your Windows VMR build command, i.e.:build -prepareMachine -c Release /p:TargetOS=windows /p:TargetArchitecture=x64 /bl /p:DotNetBuildTests=true
The text was updated successfully, but these errors were encountered: