Bug description
Hi folks, I'm seeing a new trimmer warning for IL2037 while migrating to .NET 10 which looks like it might be caused by a typo:
ILLink : error IL2037: Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteUpdateAsync<TSource>(IQueryable<TSource>, Action<UpdateSettersBuilder<TSource>>, CancellationToken): No members were resolved for 'ExecuteUpdate``1(System.Linq.IQueryable{``1},System.Collections.Generic.IReadOnlyList{ITuple})' on type 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions'.
which appears to be complaining that this signature:
ExecuteUpdate``1(System.Linq.IQueryable{``1},System.Collections.Generic.IReadOnlyList{ITuple})
doesn't resolve to:
private static int ExecuteUpdate<TSource>(this IQueryable<TSource> source, [NotParameterized] IReadOnlyList<ITuple> setters)
=> throw new UnreachableException("Can't call this overload directly");
I'm filing this ticket without a repro (for now) because it looks like this might just be caused by a backtick typo—i.e., IQueryable{``1} instead of IQueryable{``0}—and wanted to see if anyone familiar with how the linker/trimmer implements DynamicDependency might be able to confirm/reject my guess before I sink time into a repro.
(I know, I know: "user opens ticket without repro and thinks they're justified because of XYZ" is tantamount to a capital crime, but humor me?)
References
Your code
_(I know, I know: "user opens ticket without repro and thinks they're justified because of XYZ" is tantamount to a capital crime, but humor me?)_
Stack traces
ILLink : error IL2037: Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ExecuteUpdateAsync<TSource>(IQueryable<TSource>, Action<UpdateSettersBuilder<TSource>>, CancellationToken): No members were resolved for 'ExecuteUpdate``1(System.Linq.IQueryable{``1},System.Collections.Generic.IReadOnlyList{ITuple})' on type 'Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions'.
Verbose output
EF Core version
10.0.0
Database provider
No response
Target framework
.NET 10.0
Operating system
No response
IDE
No response
Bug description
Hi folks, I'm seeing a new trimmer warning for
IL2037while migrating to .NET 10 which looks like it might be caused by a typo:which appears to be complaining that this signature:
doesn't resolve to:
I'm filing this ticket without a repro (for now) because it looks like this might just be caused by a backtick typo—i.e.,
IQueryable{``1}instead ofIQueryable{``0}—and wanted to see if anyone familiar with how the linker/trimmer implementsDynamicDependencymight be able to confirm/reject my guess before I sink time into a repro.(I know, I know: "user opens ticket without repro and thinks they're justified because of XYZ" is tantamount to a capital crime, but humor me?)
References
Your code
Stack traces
Verbose output
EF Core version
10.0.0
Database provider
No response
Target framework
.NET 10.0
Operating system
No response
IDE
No response