-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Don't warn for reflection access to compiler-generated code #104757
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
Don't warn for reflection access to compiler-generated code #104757
Conversation
CompilerGeneratedMemberAccessedViaReflection = 2118, | ||
DynamicallyAccessedMembersOnTypeReferencesCompilerGeneratedMember = 2119, | ||
DynamicallyAccessedMembersOnTypeReferencesCompilerGeneratedMemberOnBase = 2120, | ||
_unused_CompilerGeneratedMemberAccessedViaReflection = 2118, | ||
_unused_DynamicallyAccessedMembersOnTypeReferencesCompilerGeneratedMember = 2119, | ||
_unused_DynamicallyAccessedMembersOnTypeReferencesCompilerGeneratedMemberOnBase = 2120, |
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.
Will we also doc that people shouldn't expect this warning anymore? We could even go as far as saying this is safe to suppress since it's likely this generates more false positives than point out real issues.
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.
Looks like we didn't doc these warnings yet so I think we can just leave them undocumented.
/ba-g "The machine restarted and Azure DevOps can't recover from restarts." |
Fixes #85042