I never had such problem in Kotlin, others languages (like Scala) does have the same semantic and it was never a problem. It seems more like a simple human mistake (and everyone does mistakes) than a bad language design.