Changing, whether one function compiles, analyzing another function bodies is just bad.I love that Kotlin’s guarantees are hard to break and almost impossible with normal code. Sacrificing null-safety or type-safety is just not an option at all.I understand where this problem comes from, I even wrote something about it myself, but I don’t think that there’s any sane way to make it much better than now. Null-safety and smart casts are awesome in Kotlin and it makes me much more productive. There’s some heated discussion there, I don’t want to bloat bugtracker with flames, but I’m very against this kind of change. The project is still in progress and I need to add a discription to use it but here a litte example to fix your problem. You can find the library on Github: GitHub - stupacki/MultiFunctions So I decided to use the power of ExtensionFunctions and wrote my own Library to make it more elegant and readable.

Before I wrote Stuff in Kotlin I used Scala and Clojure to get things done, both of them have a more elegant way to deal with multiple NonNull Values for Collection Operations and Lets, then Kotlin has out of the box.

Kotlin null check