This has been known for probably at least a year and nobody thinks it's worth addressing? Makes me wonder what else I'm going to run into with Kotlin. Maybe a compiler warning would be a good start: "Calling valid code from here can easily result in null pointer exceptions where they are ordinarily impossible" ... this feels like undefined behavior.

alexreidy: Intellij already warns about this behavior:

Actually this is no better than Java.

Hmm good to know, thanks. I must have that kind of warning turned off or something though. But I still get warned about my impossible

if (x == null) {}

that actually executes... 😑

yeah (