ILEmitTrieFactory isn't linker friendly

[davidfowl]

We're doing reflection to find methods on the Unsafe class but the pattern isn't visible to the linker.

C:\dev\git\aspnetcore\src\Http\Routing\src\Matching\ILEmitTrieFactory.cs(492,17): Trim analysis warning IL2006: Microsoft.AspNetCore.Routing.Matching.ILEmitTrieFactory.Methods.Methods(): Call to 'System.Reflection.MethodInfo.MakeGenericMethod' is not recognized. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]
C:\dev\git\aspnetcore\src\Http\Routing\src\Matching\ILEmitTrieFactory.cs(505,17): Trim analysis warning IL2006: Microsoft.AspNetCore.Routing.Matching.ILEmitTrieFactory.Methods.Methods(): Call to 'System.Reflection.MethodInfo.MakeGenericMethod' is not recognized. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]
C:\dev\git\aspnetcore\src\Http\Routing\src\Matching\ILEmitTrieFactory.cs(529,17): Trim analysis warning IL2006: Microsoft.AspNetCore.Routing.Matching.ILEmitTrieFactory.Methods.Methods(): Call to 'System.Reflection.MethodInfo.MakeGenericMethod' is not recognized. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]
C:\dev\git\aspnetcore\src\Http\Routing\src\Matching\ILEmitTrieFactory.cs(543,17): Trim analysis warning IL2006: Microsoft.AspNetCore.Routing.Matching.ILEmitTrieFactory.Methods.Methods(): Call to 'System.Reflection.MethodInfo.MakeGenericMethod' is not recognized. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]
C:\dev\git\aspnetcore\src\Http\Routing\src\Matching\ILEmitTrieFactory.cs(555,17): Trim analysis warning IL2006: Microsoft.AspNetCore.Routing.Matching.ILEmitTrieFactory.Methods.Methods(): Call to 'System.Reflection.MethodInfo.MakeGenericMethod' is not recognized. [C:\Users\davifowl\source\repos\WebApplication60\WebApplication60\WebApplication60.csproj]

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[davidfowl]

We should be able to close this one since we only use this path if runtime code generation is supported.