Interesting, I wonder how many Scala users intentionally pass around mutable objects and/or attempt to mutate non-local state. I guess for Java devs new to Sca

Interesting, I wonder how many Scala users intentionally pass around mutable objects and/or attempt to mutate non-local state. I guess for Java devs new to Scala that might seem a viable approach at first...so yes, maybe forcing the user to be explicit in the same way that the `var` keyword is required to stray into mutable territory would be a good thing -- certainly wouldn't bother those that use immutable constructs 99% of the time.