The Contains extension method of the array calls to different targets

[q7164518]

Version Used:
dotnet --version
9.0.200

C# Version Used:
preview

Steps to Reproduce:

long[] ids = [1, 2, 3];
var data = ids.Contains(1);

Expected Behavior:

System. Linq. Enumerable.Contains

Actual Behavior:

System.MemoryExtensions.Contains

Why does C# Preview have call bias, which causes expression tree parsing errors

Of course, if I don't use the C# preview, the Contains method is called correctly

[Youssef1313]

It seems this exact example was mentioned in the first-class span types proposal:

https://github.com/dotnet/csharplang/blob/285ea6828689150ee08878358854cc2dc93b4bac/proposals/first-class-span-types.md#expression-trees

Briefly mentioned in the breaking changes doc as well: https://github.com/dotnet/roslyn/blob/main/docs/compilers/CSharp/Compiler%20Breaking%20Changes%20-%20DotNet%2010.md#spant-and-readonlyspant-overloads-are-applicable-in-more-scenarios-in-c-14-and-newer

@jjonescz may be able to comment with more details.

[q7164518]

It seems this exact example was mentioned in the first-class span types proposal:

https://github.com/dotnet/csharplang/blob/285ea6828689150ee08878358854cc2dc93b4bac/proposals/first-class-span-types.md#expression-trees

Briefly mentioned in the breaking changes doc as well: https://github.com/dotnet/roslyn/blob/main/docs/compilers/CSharp/Compiler%20Breaking%20Changes%20-%20DotNet%2010.md#spant-and-readonlyspant-overloads-are-applicable-in-more-scenarios-in-c-14-and-newer

@jjonescz may be able to comment with more details.

Then ORM needs to be proactive. Okay, I get it