That's encouraging, not enforcing. Nothing stops you from importing the mutable map type. All you showed is that your code sample uses an immutable type.
On Thu, Nov 24, 2011 at 9:50 PM, Kevin Wright <[email protected]> wrote: > C'mon! > 1. Open a fresh scala REPL. No imports, no other lines of code, just a clean > standard REPL > 2. val m = Map(1->"a",2->"b",3->"c") > 3. Your challenge, should you accept it, is to manipulate m in such a way as > to change its value > 3a. and no, creating a new m doesn't count > > 2011/11/25 Cédric Beust ♔ <[email protected]> >> >> On Thu, Nov 24, 2011 at 3:42 PM, Kevin Wright <[email protected]> >> wrote: >>> >>> it embraces the same ideals of immutability that he once championed >> >> We already went through this, Scala "the language" does very little to >> enforce immutability. Hardly more than Java. >> -- >> Cédric > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
