-
Notifications
You must be signed in to change notification settings - Fork 5.3k
[mono] Fix diamond pattern encountered with static virtual interface methods #69738
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
Conversation
… interface call Small refactoring to avoid duplicated code
…al interface call
From IL, it is possible to change the access modifier when overriding a method. In such case we need to check the accessibility of the IL method and not the one that we resolve from the constrained class.
trylek
left a comment
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.
I don't really consider myself a Mono expert but to my limited knowledge this looks good, thank you!
|
The test case from the CoreCLR PR might suffer further additions so keeping this on hold until then. |
|
This still passes the latest version of the testcase, so all good. |
|
The JIT changes look ok to me. |
|
/azp run runtime-wasm lgtm |
|
No pipelines are associated with this pull request. |
|
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Test for this is added in PR #66887