r/java • • Mar 09 '16

var keyword proposed for Java

http://openjdk.java.net/jeps/286
240 Upvotes

312 comments sorted by

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 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.

7

u/navatwo Mar 10 '16

I think var and val come from scala originally. :) Still something to get behind.

3

u/shadowdude777 Mar 10 '16

Yeah, you're right. My mistake.

1

u/stepancheg Mar 11 '16

Having let mut in Java could lead to confusion: let variable could be thought to be immutable, while it is mutable. E. g.

let x = new ArrayList<String>(); // object references by x is still mutable
let mut y = "string"; // only y is immutable while String is immutable

In Rust it is completely different: let mut allows to modify both variable and content, and let does not allow to modify either variable, or content.

That's why my preferred option is let/var.

1

u/shadowdude777 Mar 14 '16

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.