Need help with scala?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

13.4K Stars 3.1K Forks Apache License 2.0 37.1K Commits 12 Opened issues


Scala 2 compiler and standard library. For bugs, see scala/bug

Services available


Need anything else?

Contributors list


This is the home of the Scala 2 standard library, compiler, and language spec.

How to contribute

Issues and bug reports for Scala 2 are located in scala/bug. That tracker is also where new contributors may find issues to work on: good first issues, help wanted.

For coordinating broader efforts, we also use the scala/scala-dev tracker.

To contribute here, please open a pull request from your fork of this repository.

Be aware that we can't accept additions to the standard library, only modifications to existing code. Binary compatibility forbids adding new public classes or public methods. Additions are made to scala-library-next instead.

We require that you sign the Scala CLA before we can merge any of your work, to protect Scala's future as open source software.

The general workflow is as follows. 1. Find/file an issue in scala/bug (or submit a well-documented PR right away!). 2. Fork the scala/scala repo. 3. Push your changes to a branch in your forked repo. For coding guidelines, go here. 4. Submit a pull request to scala/scala from your forked repo.

For more information on building and developing the core of Scala, read the rest of this README, especially for setting up your machine!

Get in touch!

In order to get in touch with other Scala contributors, join scala/contributors (Gitter) or post on (Discourse).

If you need some help with your PR at any time, please feel free to @-mention anyone from the list below, and we will do our best to help you out:

| | username | talk to me about... | --------------------------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------| |

| back end, optimizer, named & default arguments, reporters | |
| 2.12.x branch, compiler performance, weird compiler bugs, lambdas | |
| getting started, build, CI, community build, Jenkins, docs, library, REPL | |
| pattern matcher, MiMa, partest | |
| collections library, performance | |
| concurrency, futures | |
| interactions with Scala.js | |
| library, concurrency,

, warnings | |
| TASTy reader | |
| higher-kinded types, implicits, variance |

P.S.: If you have some spare time to help out around here, we would be delighted to add your name to this list!


Target the oldest branch you would like your changes to end up in. We periodically merge forward from older release branches (e.g., 2.12.x) to new ones (e.g. 2.13.x).

If your change is difficult to merge forward, you may be asked to also submit a separate PR targeting the newer branch.

If your change is version-specific and shouldn't be merged forward, put

in the PR name.

If your change is a backport from a newer branch and thus doesn't need to be merged forward, put

in the PR name.

Choosing a branch

Most changes should target 2.13.x. We are increasingly reluctant to target 2.12.x unless there is a special reason (e.g. if an especially bad bug is found, or if there is commercial sponsorship).

The 2.11.x branch is now inactive and no further 2.11.x releases are planned (unless unusual, unforeseeable circumstances arise). You should not target 2.11.x without asking maintainers first.

Repository structure

Most importantly:

+--build.sbt                 The main sbt build definition
+--project/                  The rest of the sbt build
+--src/                      All sources
   +---/library              Scala Standard Library
   +---/reflect              Scala Reflection
   +---/compiler             Scala Compiler
+--test/                     The Scala test suite
   +---/files                Partest tests
   +---/junit                JUnit tests
   +---/scalacheck           ScalaCheck tests
+--spec/                     The Scala language specification

but also:

   +---/library-aux          Scala Auxiliary Library, for bootstrapping and documentation purposes
   +---/interactive          Scala Interactive Compiler, for clients such as an IDE (aka Presentation Compiler)
   +---/intellij             IntelliJ project templates
   +---/manual               Scala's runner scripts "man" (manual) pages
   +---/partest              Scala's internal parallel testing framework
   +---/partest-javaagent    Partest's helper java agent
   +---/repl                 Scala REPL core
   +---/repl-frontend        Scala REPL frontend
   +---/scaladoc             Scala's documentation tool
   +---/scalap               Scala's class file decompiler
   +---/testkit              Scala's unit-testing kit
+--admin/                    Scripts for the CI jobs and releasing
+--doc/                      Additional licenses and copyrights
+--scripts/                  Scripts for the CI jobs and releasing
+--tools/                    Scripts useful for local development
+--build/                    Build products
+--dist/                     Build products
+--target/                   Build products

Get ready to contribute


You need the following tools: - Java SDK. The baseline version is 8 for both 2.12.x and 2.13.x. It is almost always fine to use a later SDK such as 11 or 15 for local development. CI will verify against the baseline version. - sbt

MacOS and Linux work. Windows may work if you use Cygwin. Community help with keeping the build working on Windows and documenting any needed setup is appreciated.

Tools we use

We are grateful for the following OSS licenses: - JProfiler Java profiler - YourKit Java Profiler - IntelliJ IDEA

Build setup


During ordinary development, a new Scala build is built by the previously released version, known as the "reference compiler" or, slangily, as "STARR" (stable reference release). Building with STARR is sufficient for most kinds of changes.

However, a full build of Scala is bootstrapped. Bootstrapping has two steps: first, build with STARR; then, build again using the freshly built compiler, leaving STARR behind. This guarantees that every Scala version can build itself.

If you change the code generation part of the Scala compiler, your changes will only show up in the bytecode of the library and compiler after a bootstrap. Our CI does a bootstrapped build.

Bootstrapping locally: To perform a bootstrap, run

within an sbt session. This will build and publish the Scala distribution to your local artifact repository and then switch sbt to use that version as its new
. You may then revert back with
. Note
will also write the STARR version to
so you can switch back to it with
without republishing. This will switch the sbt session to use the
directories instead of
, which avoids wiping out classfiles and incremental metadata. IntelliJ will continue to be configured to compile and run tests using the starr version in

For history on how the current scheme was arrived at, see

Building with fatal warnings: To make warnings in the project fatal (i.e. turn them into errors), run

set Global / fatalWarnings := true
in sbt (replace
with the name of a module—such as
—to only make warnings fatal for that module). To disable fatal warnings again, either
sbt, or run
set Global / fatalWarnings := false
(again, replace
with the name of a module if you only enabled fatal warnings for that module). CI always has fatal warnings enabled.

Using the sbt build

Once you've started an

session you can run one of the core commands:
  • compile
    compiles all sub-projects (library, reflect, compiler, scaladoc, etc)
  • scala
    run the REPL / compiler directly from sbt (accept options / arguments)
  • enableOptimizer
    reloads the build with the Scala optimizer enabled. Our releases are built this way. Enable this when working on compiler performance improvements. When the optimizer is enabled the build will be slower and incremental builds can be incorrect.
  • setupPublishCore
    and configures a version number based on the current Git SHA. Often used as part of bootstrapping:
    sbt setupPublishCore publishLocal && sbt -Dstarr.version= testAll
  • dist/mkBin
    generates runner scripts (
    , etc) in
  • dist/mkPack
    creates a build in the Scala distribution format in
  • junit/test
    runs the JUnit tests;
    junit/testOnly *Foo
    runs a subset
  • scalacheck/test
    runs scalacheck tests, use
    to run a subset
  • partest
    runs partest tests (accepts options, try
    partest --help
  • publishLocal
    publishes a distribution locally (can be used as
    in other sbt projects)
    • Optionally
      set baseVersionSuffix := "bin-abcd123-SNAPSHOT"
      is the git hash of the revision being published. You can also use something custom like
      . This changes the version number from
      to something more stable (
    • Note that the
      string marks the version binary compatible. Using it in sbt will cause the
      to be
      . If the version is not binary compatible, we recommend using
      , e.g.,
    • Optionally
      set publishArtifact in (Compile, packageDoc) in ThisBuild := false
      to skip generating / publishing API docs (speeds up the process).

If a command results in an error message like

a module is not authorized to depend on
, it may be that a global sbt plugin is causing a cyclical dependency. Try disabling global sbt plugins (perhaps by temporarily commenting them out in


We recommend keeping local test files in the

directory which is listed in the
of the Scala repo.

Incremental compilation

Note that sbt's incremental compilation is often too coarse for the Scala compiler codebase and re-compiles too many files, resulting in long build times (check sbt#1104 for progress on that front). In the meantime you can: - Use IntelliJ IDEA for incremental compiles (see IDE Setup below) - its incremental compiler is a bit less conservative, but usually correct.

IDE setup

We suggest using IntelliJ IDEA (see src/intellij/

Metals may also work, but we don't yet have instructions or sample configuration for that. A pull request in this area would be exceedingly welcome. In the meantime, we are collecting guidance at scala/scala-dev#668.

In order to use IntelliJ's incremental compiler: - run

in sbt to get a build and the runner scripts in
- run "Build" - "Make Project" in IntelliJ

Now you can edit and build in IntelliJ and use the scripts (compiler, REPL) to directly test your changes. You can also run the

commands in sbt. Enable "Ant mode" (explained above) to prevent sbt's incremental compiler from re-compiling (too many) files before each

Coding guidelines

Our guidelines for contributing are explained in It contains useful information on our coding standards, testing, documentation, how we use git and GitHub and how to get your code reviewed.

You may also want to check out the following resources: - The "Scala Hacker Guide" covers some of the same ground as this README, but in greater detail and in a more tutorial style, using a running example. - Scala documentation site

Scala CI

Build Status

Once you submit a PR your commits will be automatically tested by the Scala CI.

Our CI setup is always evolving. See scala/scala-dev#751 for more details on how things currently work and how we expect they might change.

If you see a spurious failure on Jenkins, you can post

as a PR comment. The scabot README lists all available commands.

If you'd like to test your patch before having everything polished for review, you can have Travis CI build your branch (make sure you have a fork and have Travis CI enabled for branch builds on it first, and then push your branch). Also feel free to submit a draft PR. In case your draft branch contains a large number of commits (that you didn't clean up / squash yet for review), consider adding

[ci: last-only]
to the PR title. That way only the last commit will be tested, saving some energy and CI-resources. Note that inactive draft PRs will be closed eventually, which does not mean the change is being rejected.

CI performs a compiler bootstrap. The first task,

, publishes a build of your commit to the temporary repository Note that this build is not yet bootstrapped, its bytecode is built using the current STARR. The version number is
is the commit hash. For binary incompatible builds, the version number is

You can use Scala builds in the validation repository locally by adding a resolver and specifying the corresponding

$ sbt
> set resolvers += "pr" at ""
> set scalaVersion := "2.12.2-bin-abcd123-SNAPSHOT"
> console

"Nightly" builds

The Scala CI builds nightly download releases and publishes them to .

Using a nightly build in sbt is explained in this Stack Overflow answer

Although we casually refer to these as "nightly" builds, they aren't actually built nightly, but "mergely". That is to say, a build is published for every merged PR.

Scala CI internals

The Scala CI runs as a Jenkins instance on, configured by a chef cookbook at scala/scala-jenkins-infra.

The build bot that watches PRs, triggers testing builds and applies the "reviewed" label after an LGTM comment is in the scala/scabot repo.

Community build

The Scala community build is an important method for testing Scala releases. A community build can be launched for any Scala commit, even before the commit's PR has been merged. That commit is then used to build a large number of open-source projects from source and run their test suites.

To request a community build run on your PR, just ask in a comment on the PR and a Scala team member (probably @SethTisue) will take care of it. (details)

Community builds run on the Scala Jenkins instance. The jobs are named

. See the scala/community-builds repo.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.