5 ms·

Yes! Then we could call it "kotlin" :)

• happymellon 3y ago
  Hopefully not. > val a: Int = 1 I wouldn't want to inflict that on anyone.
  • winrid 3y ago
    You don't need to have the "int" there, though, right? You can just do "val a = 1" [0] Don't get me wrong, I still pick Java over Kotlin, but I thought ktl had type inference. Even Java has "var a = 1" now. I just wish we had optional named parameters in Java, that's like, my biggest issue with the language. [0] https://www.oreilly.com/library/view/kotlin-programming-the/9780135165188/ch02s05.html https://www.oreilly.com/library/view/kotlin-programming-the/...
    • happymellon 3y ago
      I took that example from the Kotlin homepage. I've not used Kotlin, but since Scala recommends that you include the type declaration if you know what it is, I assumed that Kotlin did as well. If their example is bad, then apologies! Optional named parameters and also default values would be great. The stuff that gets used by the most in this codebase is the `allParameterConstructor` for enums and the `slf4j` annotation. Without those two I could probably remove the Lombok dependency.