In fact, I would go a step further on this. Really knowing the performance characteristics of the very rich selection of collections in Scala is one of the best ways I can think of to improve your Scala proficiency and the efficiency of your applications. I would find it hard to go back to Java collections alone at this point - I only really used ArrayList and ConcurrentHashMap there anyway. Vector in particular is an incredible, immutable datastructure. That said, I do still use the Guava map maker (with a nice Scala wrapper) as I have yet to find a better solution for thread safe, performant, key based caching on Scala (using a synchronized map of futures works, but it's a bit clunky compared with mapmaker).
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/3pa6x1T3L48J. 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.
