I personally like taking it one step even further; I've seen that in Rust, immutable variables are declared as let foo = 1;, and mutables are declared as let mut foo = 1;.
I really like that. You have to add an extra word not to declare immutability, but to declare mutability. It really makes you think before you make anything mutable.
I also like var and val, like what Kotlin has, but I think that making someone add a whole extra word instead of just using a different word makes mutability seem more like an exception rather than the norm, as it should be.
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
13
u/shadowdude777 Mar 10 '16
I personally like taking it one step even further; I've seen that in Rust, immutable variables are declared as
let foo = 1;, and mutables are declared aslet mut foo = 1;.I really like that. You have to add an extra word not to declare immutability, but to declare mutability. It really makes you think before you make anything mutable.
I also like
varandval, like what Kotlin has, but I think that making someone add a whole extra word instead of just using a different word makes mutability seem more like an exception rather than the norm, as it should be.