MP-3611: Add regression test proving internal-API hierarchy misattribution is already fixed - #1563
Open
Magda Stożek (magdzikk) wants to merge 1 commit into
Open
Conversation
…ution is already fixed
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Investigated MP-3611 as part of the Kotlin-inline-fun false-positive ticket family. This one isn't actually related to Kotlin inlining — it's a class-hierarchy attribution issue, where an
@ApiStatus.Internaltype is implemented by a platform ancestor class encountered while the verifier walks a plugin class's own inheritance chain.I checked that this issue no longer reproduces on current master - it was fixed by #580.
I'm adding a regression test for that case. (I also checked that it fails when the fix is removed)