News for hackers. Stuff that matters.
Re:Representing the Impractical and Impossible with JDK 10 “... by saagarjha on Sunday March 04, 2018 @03:47PM (#16516622)
How so?
Re:Representing the Impractical and Impossible with JDK 10 “... by rbonvall on Sunday March 04, 2018 @04:03PM (#16516703)
I'm sure he means `val` as in Scala, where it is used to define a name that cannot be rebound:

    val x = 1
    var y = 2
    x = 3     // compile error
    y = 4     // ok
It makes it easier to read code since you don't have to keep track of changes in your head.
Re:Representing the Impractical and Impossible with JDK 10 “... by saagarjha on Sunday March 04, 2018 @04:13PM (#16516777)
Yes, this would be a nice addition, but I think final var might be able to stand in for it as of right now. One issue if it was adopted might be that “final” in Java doesn’t actually mean a whole lot, since there aren’t a lot of value types where mutation can be detected.
Re:Representing the Impractical and Impossible with JDK 10 “... by blattimwind on Sunday March 04, 2018 @04:40PM (#16516931)
Or as in Kotlin.
Re:Representing the Impractical and Impossible with JDK 10 “... by krotton on Sunday March 04, 2018 @04:06PM (#16516735)
I guess the parent meant val as synonymous to final var, i.e. immutable.
Re:Representing the Impractical and Impossible with JDK 10 “... by saagarjha on Sunday March 04, 2018 @04:15PM (#16516792)
var, let, val, there are so many of these and they all mean different things in different languages! It makes it hard to talk about them.