ForkDatabricks (DBRX)Databricks (DBRX)published Apr 25, 2023seen 5d

databricks/scala

forked from scala/scala

Open original ↗

Captured source

source ↗
published Apr 25, 2023seen 5dcaptured 11hhttp 200method plain

databricks/scala

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

License: Apache-2.0

Stars: 2

Forks: 0

Open issues: 0

Created: 2023-04-25T08:03:39Z

Pushed: 2026-05-11T11:59:16Z

Default branch: 2.13.x

Fork: yes

Parent repository: scala/scala

Archived: no

README:

Welcome!

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

If you want to visit the Scala 3 repository, go to the lampepfl/dotty.

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 the \#scala-contributors channel on the Scala Discord chat, or post on contributors.scala-lang.org (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... | --------------------------------------------------------------------------------------------------|----------------------------------------------------------------|---------------------------------------------------| | `@lrytz` | back end, optimizer, named & default arguments, reporters | | `@retronym` | 2.12.x branch, compiler performance, weird compiler bugs, lambdas | | `@SethTisue` | getting started, build, CI, community build, Jenkins, docs, library, REPL | | `@dwijnand` | pattern matcher, MiMa, partest | | `@som-snytt` | warnings/lints/errors, REPL, compiler options, compiler internals, partest | | `@Ichoran` | collections library, performance | | `@viktorklang` | concurrency, futures | | `@sjrd` | interactions with Scala.js | | `@NthPortal` | library, concurrency, scala.math, LazyList, Using, warnings | | `@bishabosha` | TASTy reader | | `@joroKr21` | 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!

Branches

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 [nomerge] in the PR name.

If your change is a backport from a newer branch and thus doesn't need to be merged forward, put [backport] 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:

scala/
+--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:

scala/
+---/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

Requirements

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.…

Excerpt shown — open the source for the full document.