-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Add trim analysis warnings for delegate creation #92427
Conversation
The ILLink analyzer was not producing warnings for annotated methods, lambdas, or local functions accessed for delegate creation. Some ExpectedWarnings for ILLink/NativeAot were updated to avoid relying on the name of the compiler-generated methods for lambdas or local functions, because the analyzer reports the warnings as: IL2111: Method 'lambda expression' with parameters... is accessed via reflection.
Tagging subscribers to this area: @dotnet/area-meta Issue DetailsThe ILLink analyzer was not producing warnings for annotated methods, lambdas, or local functions accessed for delegate creation. Some ExpectedWarnings for ILLink/NativeAot were updated to avoid relying on the name of the compiler-generated methods for lambdas or local functions, because the analyzer reports the warnings as: IL2111: Method 'lambda expression' with parameters... is accessed via reflection.
|
src/tools/illink/src/ILLink.RoslynAnalyzer/DataFlow/LocalDataFlowVisitor.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the RUC question - this looks good.
@dotnet-policy-service rerun |
The ILLink analyzer was not producing warnings for annotated methods, lambdas, or local functions accessed for delegate creation.
Some ExpectedWarnings for ILLink/NativeAot were updated to avoid relying on the name of the compiler-generated methods for lambdas or local functions, because the analyzer reports the warnings as:
IL2111: Method 'lambda expression' with parameters... is accessed via reflection.
Fixes #84918