This concept allows evolving language easier in th...

# announcements

[orangy]

This concept allows evolving language easier in the future. You can’t normally add another hard keyword without breaking some code. E.g. we added suspend in 1.1 without breaking any code that might be using val suspend = shouldSuspendUser()

[trubesv]

Great thinking, kind of why I like Kotlin more and more each day 🙂
My reaction was about the dirty snippet (no offense intended @kevinmost):

public val private: public = public()
class public {
}

[kevinmost]

that snippet is terrible and I hope people try to avoid abusing soft keywords like this, haha

[trubesv]

IntelliJ should display a "BAD PRACTICE" message

[trubesv]

in bold red letters

[trubesv]

flashing on screen with a strident sound

[melston]

and sending email to your boss!

[orangy]

Disables Kotlin plugin for 24 hours and forces you to write code in Java.

[trubesv]

Without lambdas

[artem_zin]

Actually Kotlin already has a tool to prohibit that — called Kapt (stands for Kotlin Absurd Prevention Tool) , which doesn’t escape things like public properly so they slip into generated .java files and then javac fails your build lol

[orangy]

@yan

[artem_zin]

That’s a known issue https://youtrack.jetbrains.com/issue/KT-18691

[artem_zin]

But I can’t tell from the fix commit if it helps with things like val public: Boolean <https://github.com/jetbrains/kotlin/commit/a98313797839b8104e79a6a75f6f779d5ef5d315>

[yan]

@artem_zin Newer versions of Kotlin should simply ignore declarations with “Java-incompatible” names.