Repository files navigation

This Scala standard module contains the packagescala.collection.parallel, with all of the parallel collections thatused to be part of the Scala standard library (in Scala 2.10 through 2.12).

For Scala 3 and Scala 2.13, this module is a separate JAR that can beomitted from projects that do not use parallel collections.

• https://docs.scala-lang.org/overviews/parallel-collections/overview.html
• https://javadoc.io/doc/org.scala-lang.modules/scala-parallel-collections_2.13

This module is community-maintained, under the guidance of the Scala team at Akka. If you areinterested in participating, please jump right in on issues and pullrequests.

To depend on scala-parallel-collections in sbt, add this to yourbuild.sbt:

libraryDependencies+="org.scala-lang.modules"%%"scala-parallel-collections"%"<version>"

In your code, adding this import:

importscala.collection.parallel.CollectionConverters._

will enable use of the.par method as in earlier Scala versions.

This module is published only for the Scala 3 and 2.13, so in across-built project, the dependency should take this form:

libraryDependencies++= {CrossVersion.partialVersion(scalaVersion.value)match {caseSome((2, major))if major<=12=>Seq()case _=>Seq("org.scala-lang.modules"%%"scala-parallel-collections"%"<version>")  }}

This way of testingscalaVersion is robust across varying Scalaversion number formats (nightlies, milestones, release candidates,community build, etc).

Using.par is problematic in a cross-built project, since in Scala2.13+ theCollectionConverters._ import shown above is necessary, butin earlier Scala versions, that import will not compile.

You may able to avoid the problem by directly constructing yourparallel collections rather than going through.par. For otherpossible workarounds, see#22,which is still under discussion.

As with other Scala standard modules, build and release infrastructureis provided by thesbt-scala-module sbtplugin.