How to bypass Kotlin null safety! https://www.linkedin.com/posts/erfan-sn_kotlin-code-null-activity-7129874982297382912-muhO?utm_source=share&utm_medium=member_android

I had to try it out, and you’re right! https://pl.kotl.in/jwmNL7R0S

But it is as expected, right? The order of initialisation makes it in a way that message in outer is not defined yet when asked in the inner class constructor.

Yes, because of the order or operations, it’s to be expected. But it being a non-nullable val; Would make you think it wouldn’t give you null. Maybe some KLint or Detekt rule should be made to warn about this.

Yes, it seems that the result is correct, because in the latest version of Java, the result is equal to null, but the compiler should inform about it anyway.

Its almost as if you shouldnt be writing code like this in the first place 🧌