Okay wait, I might have messed my wording up there...
# announcements
r
Okay wait, I might have messed my wording up there. The Kotlin compiler uses static analysis to keep you from messing up your nulls while in Kotlin, but as the JVM doesn't make the distinction between nullable and non nullable types on the bytecode level, it can't enforce Java (and other) code to respect those. To counter that Kotlin inserts null-checks at all the possible interaction points between kotlin code and external code, so IF any outside code does not respect the nullability rules the program will crash immediately, rather than introducing obscure bugs. You can't really do any better than that in that regard on the JVM.
👏 2