-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[mono] Implement IgnoresAccessChecksToAttribute support #48558
[mono] Implement IgnoresAccessChecksToAttribute support #48558
Conversation
Tagging subscribers to this area: @CoffeeFlux Issue DetailsSystem.Runtime.CompilerServices.IgnoresAccessChecksToAttribute is like the reverse of The interesting thing is that the DynamicProxy dynamically generates Fixes #47989
|
Tagging subscribers to this area: @CoffeeFlux Issue DetailsSystem.Runtime.CompilerServices.IgnoresAccessChecksToAttribute is like the reverse of The interesting thing is that the DynamicProxy dynamically generates Fixes #47989
|
7e4e590
to
708a502
Compare
System.Runtime.CompilerServices.IgnoresAccessChecksToAttribute is like the reverse of InternalsVisibleTo - it's added to an assembly to indicate that that assembly can call non-public methods from the specified assembly. The interesting thing is that the DynamicProxy dynamically generates the attribute, so it is not explicitly declared in CoreLib. Fixes dotnet#47989
check that calling private/internal methods in another assembly throws. check that calling a private method in the same assembly throws.
708a502
to
bdf249e
Compare
Thank you @lambdageek! |
System.Runtime.CompilerServices.IgnoresAccessChecksToAttribute is like the reverse of
InternalsVisibleTo - it's added to an assembly to indicate that that
assembly can call non-public methods from the specified assembly.
The interesting thing is that the DynamicProxy dynamically generates
the attribute, so it is not explicitly declared in CoreLib.
Fixes #47989