Fix Type comparison (v2) in TurboModuleInteropUtils.kt #50794
Closed
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.
Summary:
instead of explictly specifying fully qualified Java boxed types, use proper Kotlin syntax to refer to it.
👉 Notes on Java <> Kotlin type mapping !!!
See: Kotlin's Mapped Types; https://kotlinlang.org/docs/java-interop.html#mapped-types
Booleanmaps to Java's primitive typebooleanand not boxed TypeBooleanBooleanmaps toBoolean?in KotlinSo in Kotlin,
Boolean::class.javarefers to Java primitive typeClass<boolean>which is equivalent toBoolean::class.javaPrimitiveTypeBoolean::class.javaObjectType==Class<Boolean>TIP: When dealing with Java primitive types using reflection, use
::class.javaPrimtiveTypeor::class.javaObjectTypeto avoid the confusion with using plain::class.java.Differential Revision: D73224138