Scala collections and Java collections correspond to transformation relationships

Syn Good son source: Http://www.cnblogs.com/cssdongl reprint please indicate the source

When you encode in Scala, you often encounter cases where Scala collections and Java collections Convert to each other, specifically mark, to deepen memory

Scala.collection.Iterable <=> java.lang.Iterable

Scala.collection.Iterable <=> java.util.Collection

Scala.collection.Iterator <=> java.util. {Iterator, enumeration}

Scala.collection.mutable.Buffer <=> Java.util.List

Scala.collection.mutable.Set <=> Java.util.Set

Scala.collection.mutable.Map <=> java.util. {Map, Dictionary}

Scala.collection.mutable.ConcurrentMap <=> Java.util.concurrent.ConcurrentMap

Scala.collection.Seq = Java.util.List

Scala.collection.mutable.Seq = Java.util.List

Scala.collection.Set = Java.util.Set

Scala.collection.Map = Java.util.Map

Java.util.Properties = scala.collection.mutable.map[string, String]

Scala.collection.JavaConversions can be used to quickly convert, such as the Java list quickly into Scala's buffer

Val scalalist = Javaconversions.asscalabuffer (javalist)

Scala collections and Java collections correspond to transformation relationships