Skip to content
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

Fix devirtualization in shared generic context #53255

Merged
merged 1 commit into from
May 26, 2021

Conversation

davidwrighton
Copy link
Member

In circumstances where the JIT doesn't provide exact enough details about the impl type and interface method to identify exactly which method should be called

  • In particular, when the impl class implements multiple copies of the target interface, and they are canonically compatible with the interface method that is to be called
  • Simply disable devirtualization for these scenarios

Fixes #51982

…xact enough details about the impl type and interface method to identify exactly which method should be called

- In particular, when the impl class implements multiple copies of the target interface, and they are canonically compatible with the interface method that is to be called
- Simply disable devirtualization for these scenarios
Copy link
Member

@trylek trylek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, thanks for fixing this!

@davidwrighton davidwrighton merged commit 5c875e4 into dotnet:main May 26, 2021
@davidwrighton davidwrighton deleted the fix_51982 branch May 26, 2021 18:06
@ghost ghost locked as resolved and limited conversation to collaborators Jun 25, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect devirtualization in shared generic context
2 participants