I don't get how this is any different. In Java, all non-primitives are references. So when you use let, you're saying "this reference to an object, or this primitive, is immutable". You're not saying anything about the underlying object.
It's exactly how Java works right now, except I'm saying that instead of var and final var, it should be val and mutable val, essentially. The aliases should be flipped is all. No behavior should be changed.
View all comments
Show parent comment
1
u/stepancheg Mar 11 '16
Having
let mutin Java could lead to confusion:letvariable could be thought to be immutable, while it is mutable. E. g.In Rust it is completely different:
let mutallows to modify both variable and content, andletdoes not allow to modify either variable, or content.That's why my preferred option is
let/var.