You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
C# 14 is bringing first-class spans, which changes the compiler resolution of method invocations, causes MemoryExtensions.Contains() (accepting spans) to be resolved instead of the traditional Enumerable.Contains. This can cause issues with LINQ providers, and likely would need reacting to in MEVD LINQ filters as well. We can integrate this logic into the FilterTranslationPreprocessor.
changed the title [-][MEVD] Ensure Contains compatibility with C# 14 first-class spans[/-][+].Net: [MEVD] Ensure Contains compatibility with C# 14 first-class spans[/+]on Jun 17, 2025
Activity
[-][MEVD] Ensure Contains compatibility with C# 14 first-class spans[/-][+].Net: [MEVD] Ensure Contains compatibility with C# 14 first-class spans[/+]github-actions commentedon Sep 17, 2025
This issue is stale because it has been open for 90 days with no activity.
Support MemoryExtensions.Contains in LINQ filters
Support MemoryExtensions.Contains in LINQ filters
Support MemoryExtensions.Contains in LINQ filters
.Net: [MEVD] Support MemoryExtensions.Contains in LINQ filters (#13263)
feat: Add C# 14 MemoryExtensions.Contains support to BingTextSearch
feat: Add C# 14 MemoryExtensions.Contains support to BingTextSearch
feat: Add C# 14 MemoryExtensions.Contains support to BingTextSearch