Fix Kotlin Object issue #1562
Merged
Fix Kotlin Object issue #1562
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related to: #1563
Currently, due to an incorrect test, we had regressed the support of Kotlin in the runtime.
Kotlin
objects are compiled to a regular class at bytecode level and the special thing about them is a compiler-generatedINSTANCEfield of the same type as the class.In a commit included in 6.3.0 we have stripped the
INSTANCEfield and broken the Kotlinobjectsupport.This PR fixes the issue by gathering the
INSTANCEfield checking by name and type. There seems to be no way to get information if the currently parsed class is a Kotlinobjectfrom the Kotlin metadata.