Fix sealing of types that were not concretely instantiated #73218
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #73076.
Because of the generic interface method use, the compiler didn't generate a concrete instantiation of one of the generic types anywhere and we were incorrectly sealing it, causing a bad devirtualization.
The fix is to look at template type instantiations too.
I'm also adding an unrelated regression test for scenarios I fixed in #64497. We could push the regression test through that PR but I've only edited the branch through GitHub UI and this is easier...
Cc @dotnet/ilc-contrib