Merge branch 'main' into patch-2

Author: kubukoz

Gemfile.lock

@@ -264,11 +264,11 @@ GEM
     minitest (5.25.4)
     net-http (0.6.0)
       uri
-    nokogiri (1.18.8-arm64-darwin)
+    nokogiri (1.18.9-arm64-darwin)
       racc (~> 1.4)
-    nokogiri (1.18.8-x64-mingw-ucrt)
+    nokogiri (1.18.9-x64-mingw-ucrt)
       racc (~> 1.4)
-    nokogiri (1.18.8-x86_64-linux-gnu)
+    nokogiri (1.18.9-x86_64-linux-gnu)
       racc (~> 1.4)
     octokit (4.25.1)
       faraday (>= 1, < 3)
@@ -287,7 +287,7 @@ GEM
     rb-fsevent (0.11.2)
     rb-inotify (0.11.1)
       ffi (~> 1.0)
-    rexml (3.4.1)
+    rexml (3.4.2)
     rouge (3.30.0)
     ruby-rc4 (0.1.5)
     rubyzip (2.4.1)

_config.yml

@@ -15,9 +15,9 @@ keywords:
 - Document
 - Guide
 
-scala-version: 2.13.16
+scala-version: 2.13.17
 scala-212-version: 2.12.20
-scala-3-version: 3.7.1
+scala-3-version: 3.7.4
 
 collections:
   style:

_ja/getting-started/install-scala.md

@@ -178,4 +178,4 @@ IDE の使用に慣れている場合は、IDE から _Main.scala_ のコード
 他の Scala ユーザーとすぐに連絡を取りたい場合は、多くのメーリングリストやリアルタイムのチャットルームがあります。これらのリソースのリストや、どこに問い合わせればよいかについては、[コミュニティページ](https://scala-lang.org/community/)をご覧ください。
 
 ### (日本語のみ追記)
-Scala について日本語で質問したい場合、Twitterでつぶやくと気づいた人が教えてくれます。
+Scala について日本語で質問したい場合、X（旧Twitter）でつぶやくと気づいた人が教えてくれます。

_overviews/FAQ/index.md

@@ -27,7 +27,7 @@ See our [Community page](https://scala-lang.org/community/).
 
 ### What's a good book about Scala?
 
-Our [Books page](https://docs.scala-lang.org/books.html) lists a few
+Our [Books page](https://docs.scala-lang.org/books.html) lists some
 especially popular, well-known books.
 
 We don't have a list of all the Scala books that
@@ -39,6 +39,17 @@ ask for book recommendations. You'll get more helpful
 answers if you provide some information about your background and your
 reasons for wanting to learn Scala.
 
+### What's a good video course about Scala?
+
+Our [Online Courses page](https://docs.scala-lang.org/online-courses.html)
+lists some especially popular, well-known courses.
+
+As with books, you can go on the \#scala-users room [on
+Discord](https://discord.com/invite/scala) or another community forum and
+ask for online course recommendations. You'll get more helpful
+answers if you provide some information about your background and your
+reasons for wanting to learn Scala.
+
 ### Should I learn Scala 2, or Scala 3?
 
 Don't sweat the decision too much.  You can't go far wrong either
@@ -351,14 +362,14 @@ setting in a multi-project build.
 
 For example, if you add this to your `build.sbt`:
 
-    scalaVersion := "2.13.16"
+    scalaVersion := "2.13.17"
 
 that's a "bare" setting, and you might expect it to apply build-wide.
 But it doesn't. _It only applies to the root project._
 
 In many cases one should instead write:
 
-    ThisBuild / scalaVersion := "2.13.16"
+    ThisBuild / scalaVersion := "2.13.17"
 
 Other possibilities include:
 

_overviews/contribute/bug-reporting-guide.md

@@ -65,7 +65,7 @@ If you cannot find your issue in the issue tracker, create a new bug. The detail
 
 Please make sure to fill in as many fields as possible. Make sure you've indicated the following:
 
- 1. **Exact Scala version** that you are using. For example, `2.13.16` or `3.3.4`. If the bug happens in multiple versions indicate all of them.
+ 1. **Exact Scala version** that you are using. For example, `2.13.17` or `3.3.4`. If the bug happens in multiple versions indicate all of them.
  2. **The component** that is affected by the bug. For example, the Standard Library, Scaladoc, etc.
  3. **Labels** related to your issue. For example, if you think your issue is related to the typechecker, and if you have successfully minimized your issue, label your bug as "typechecker" and "minimized". Issue tracker will suggest names for existing labels as you type them so try not to create duplicates.
  4. **Running environment**. Are you running on Linux? Windows? What JVM version are you using?

_overviews/core/binary-compatibility-of-scala-releases.md

@@ -20,10 +20,10 @@ We distinguish forward and backward compatibility (think of these as properties
 Thus, backward compatibility precludes the removal of (non-private) methods, as older versions could call them, not knowing they would be removed, whereas forward compatibility disallows adding new (non-private) methods, because newer programs may come to depend on them, which would prevent them from running on older versions (private methods are exempted here as well, as their definition and call sites must be in the same source file).
 
 #### Guarantees and Versioning
-For Scala 2, the *minor* version is the *third* number in a version, e.g., 16 in v2.13.16.
+For Scala 2, the *minor* version is the *third* number in a version, e.g., 17 in v2.13.17.
 The major version is the second number, which is 13 in our example.
 
-Scala 2 up to 2.13.16 guarantees both backward and forward compatibility across *minor* releases within a single major release.
+Scala 2 up to 2.13.17 guarantees both backward and forward compatibility across *minor* releases within a single major release.
 This is about to change now that [SIP-51 has been accepted](https://docs.scala-lang.org/sips/drop-stdlib-forwards-bin-compat.html), future Scala 2.13 releases may be backward compatible only.
 
 For Scala 3, the minor version is the *second* number in a version, e.g., 2 in v3.2.1.

_overviews/core/futures.md

@@ -1181,7 +1181,7 @@ object Test extends App {
         completion match {
           case Failure(exception) if exception.getCause != null =>
             println(s"  caused by ${exception.getCause}")
-          _ => ()
+          case _ => ()
         }
       }
     } catch {

_overviews/core/nightlies.md

@@ -8,80 +8,89 @@ We regularly publish nightly versions of both Scala 3 and 2 so that users can pr
 
 Here's how to find and use these versions.
 
-## Scala 3
+## General information on nightlies
 
-Scala 3 nightly versions are published to Maven Central. If you know the full version number of the nightly you want to use, you can use it just like any other Scala 3 version.
+### Scala 3
 
-One quick way to get that version number is to visit [https://dotty.epfl.ch](https://dotty.epfl.ch) and look in the upper left corner.
+Scala 3 nightly versions are published to [https://repo.scala-lang.org](https://repo.scala-lang.org). Historically, they used to be published to Maven Central. Old nightly versions of Scala 3 (all the way until `3.8.0-RC1-bin-20250822-658c8bd-NIGHTLY` in August 2025) are still available there, as well as via [https://repo.scala-lang.org](https://repo.scala-lang.org).
 
-Another way is to scrape Maven Central, as shown in this script: [https://raw.githubusercontent.com/VirtusLab/community-build3/master/scripts/lastVersionNightly.sc](https://raw.githubusercontent.com/VirtusLab/community-build3/master/scripts/lastVersionNightly.sc)
+If you know the full version number of the nightly you want to use, you can use it just like any other Scala 3 version.
 
-A third way is to use [scala-cli](https://scala-cli.virtuslab.org), as follows. (Since Scala 3.5.0, the `scala` command runs `scala-cli`.)
+There are a number of ways to get that version number, as listed below.
 
-### scala-cli
+### Scala 2
 
-You can run nightlies with commands such as:
-
-    scala-cli -S 3.nightly
-    scala-cli -S 3.3.nightly
-
-The default command is `repl`, but all the other scala-cli subcommands such as `compile` and `run` work, too. It also works with `//>` directives in your script itself, for example:
+We informally refer to Scala 2 “nightly” versions, but technically it's a misnomer. A so-called “nightly” is built for every merged PR in the Scala 2 repo.
 
-    //> using scala 3.nightly
-
-See this [scala-cli doc page](https://scala-cli.virtuslab.org/docs/commands/compile#scala-nightlies) for details.
+Similarly to Scala 3 nightlies, they are available at [https://repo.scala-lang.org](https://repo.scala-lang.org).
 
-## Scala 2.13 or 2.12
+## How to use nightly versions
 
-We informally refer to Scala 2 “nightly” versions, but technically it's a misnomer. A so-called “nightly” is built for every merged PR.
+### Scala CLI
 
-Scala 2 nightly versions are published to a special resolver. Unless you are using scala-cli, you'll need to add that resolver to your build configuration in order to use these versions.
+Scala CLI is the official runner of the language and has nightlies available without any extra configuration. From Scala 3.5.0 and on it's available under the `scala` command in Scala 3 installations. It can also be installed separately as `scala-cli`.
 
-### quick version (sbt)
+Note: The nightly repository is supported since Scala CLI v1.9.0 onwards (or `scala` installed with Scala 3.7.3 or newer).
 
-    Global / resolvers += "scala-integration" at
-      "https://scala-ci.typesafe.com/artifactory/scala-integration/"
-    scalaVersion := "2.13.15-bin-abcd123"
+You can run nightlies with commands such as:
 
-For a 2.12 nightly, substitute e.g. `2.12.20` for `2.13.15`; in either case, it's the version number of the _next_ release on that branch.
+    scala -e 'println("Hello") -S 3.nightly
+    scala -e 'println("Hello") -S 3.3.nightly
+    scala -e 'println("Hello") -S 2.13.nightly
+    scala -e 'println("Hello") -S 2.nightly # same as 2.13.nightly
+    scala -e 'println("Hello") -S 2.12.nightly
 
-For `abcd123`, substitute the first 7 characters of the SHA of the latest commit to the [2.13.x branch](https://github.com/scala/scala/commits/2.13.x) or [2.12.x branch](https://github.com/scala/scala/commits/2.12.x) that has a green checkmark. (Clicking the checkmark will show a CI job name with the whole version in its name.)
+The default command is `repl` (unless sources are passed, in which case it switches to `run`), but all the other scala-cli subcommands such as `compile` and `run` work, too. It also works with `//> using` directives in your script itself, for example:
 
-A quick way to find out the full version number of a current nightly is to use [scala-cli](https://scala-cli.virtuslab.org), as follows.
+    //> using scala 3.nightly
+    //> using scala 3.3.nightly
+    //> using scala 2.nightly
+    //> using scala 2.13.nightly
+    //> using scala 2.12.nightly
 
-### quick version (scala-cli)
+See this [scala-cli doc page](https://scala-cli.virtuslab.org/docs/commands/compile#scala-nightlies) for details.
 
-You can run nightlies with:
+### Get it from the nightly website
 
-    scala-cli -S 2.13.nightly
-    scala-cli -S 2.nightly     # same as 2.13.nightly
-    scala-cli -S 2.12.nightly
+A quick way to get that version number is to visit [https://nightly.scala-lang.org](https://nightly.scala-lang.org) and look in the upper left corner.
 
-The default command is `repl`, but all the other scala-cli subcommands such as `compile` and `run` work, too. It also works with `//>` directives in your script itself, for example:
+### Check the repository, directly
 
-    //> using scala 2.nightly
+Another way is to scrape the repository, as shown in this script: [https://raw.githubusercontent.com/VirtusLab/community-build3/master/scripts/lastVersionNightly.sc](https://raw.githubusercontent.com/VirtusLab/community-build3/master/scripts/lastVersionNightly.sc)
 
-### Longer explanation
+### SBT
 
-We no longer publish `-SNAPSHOT` versions of Scala 2.
+To use recent nightlies with SBT, adding the appropriate resolver to the build configuration is necessary.
 
-But the team does publish nightly versions, each with its own fixed version number. The version number of a nightly looks like e.g. `2.13.1-bin-abcd123`. (`-bin-` signals binary compatibility to sbt; all 2.13.x releases since 2.13.0 are binary compatible with each other.)
+    ThisBuild / scalaVersion := "3.8.0-RC1-bin-20250916-eb1bb73-NIGHTLY"
+    ThisBuild / resolvers += Resolver.scalaNightlyRepository
+    lazy val root = (project in file("."))
+      .settings(name := "sbt-with-scala-nightlies")
 
-To tell sbt to use one of these nightlies, you need to do three things.
+Also note that SBT 1.11.5 or newer is necessary.
 
-First, add the resolver where the nightlies are kept:
+### Mill
 
-    Global / resolvers += "scala-integration" at
-      "https://scala-ci.typesafe.com/artifactory/scala-integration/"
+To use recent nightlies with Mill, a custom resolver for the initial bootstrap of the build is needed. 
+Here's an example `build.mill` file:
 
-Second, specify the Scala version:
+    package build
+    import mill.*
+    import mill.api.*
+    import scalalib.*
 
-    scalaVersion := "2.13.1-bin-abcd123"
+    def scalaNightlyRepo = "https://repo.scala-lang.org/artifactory/maven-nightlies"
 
-But that isn't a real version number. Manually substitute a version number containing the 7-character SHA of the last commit in the [scala/scala repository](https://github.com/scala/scala) for which a nightly version was published.  Look at [https://travis-ci.org/scala/scala/branches](https://travis-ci.org/scala/scala/branches) and you'll see the SHA in the upper right corner of the 2.13.x (or 2.12.x) section.
+    object project extends ScalaModule {
+      def jvmWorker = ModuleRef(CustomJvmWorkerModule)
+      override def scalaVersion = "3.8.0-RC1-bin-20250916-eb1bb73-NIGHTLY"
+      override def repositories = Task { super.repositories() ++ Seq(scalaNightlyRepo)}
+    }
 
-As soon as 2.13.1 is released, the version number in the nightly will bump to 2.13.2, and so on.
+    object CustomJvmWorkerModule extends JvmWorkerModule, CoursierModule {
+      override def repositories = Task { super.repositories() ++ Seq(scalaNightlyRepo)}
+    }
 
-If you have a multiproject build, be sure you set these settings across all projects when you modify your build definition. Or, you may set them temporarily in the sbt shell with `++2.13.1-bin-abcd123` (sbt 0.13.x) or `++2.13.1-bin-abcd123!` (sbt 1.x; the added exclamation point is necessary to force a version not included in `crossScalaVersions` to be used).
+Note how the custom `JvmWorkerModule` is necessary with the added repository. It is not enough to just define it as a repository for the module dependencies.
 
-Ideally, we would suggest an automated way to ask Travis-CI for the right SHA. This is presumably possible via Travis-CI's API, but as far as we know, nobody has looked into it yet. (Is there a volunteer?)
+Also note that Mill 1.0.5 or newer is necessary for this.