20 karma · joined February 19, 2013
I still don't understand why you consider having a compiler-enforced restriction on mutation worse than letting readers figure out what was the developer's intent.
In Java, the only "downside" is having to add "final" as a modifier, which is negligible.
In Scala, the alternative is to declare that variable as "var" instead of "val". When would you ever choose var over val if your object isn't supposed to mutate?
val and final have stronger meanings when your objects are immutable. True immutability makes reasoning far easier than just referential immutability.
Pattern matching offers mainly correctness and conciseness, maybe the correctness part should have been emphasized more.
List<T> l = new ArrayList<T>();
is preferred to this: ArrayList<T> l = new ArrayList<T>();
Of course, it would be nice for the compiler to assume the latter if no type is specified on the left side.> If you are a current Firefox Sync user, we’ll continue to sync your data between your devices.
So I guess the old option will still be maintained, at least during the testing phase.
Also, Google Glass may be constantly recording in private places usually without CCTV: homes, dinner tables, meetings, etc.
In any case, the deep-rooted corruption of her administration (and practically all others decades before it) is a symbol of Argentine culture.
Argentine here, you can buy SIM cards literally everywhere. Vendors will even sell them to you on trains.