I can’t say what was the reasons exactly as I’m not a Kotlin author, but I believe pretty much the same reason we had a stupid idea of removing the old good, simple and straightforward goto. It is a lower-level construct which have cleaner, high-level alternatives. Also, for doesn’t provide too much benefits over the while.
7 Likes