diff --git a/_overviews/FAQ/index.md b/_overviews/FAQ/index.md
index 1316dbdda5..fbb4fe4183 100644
--- a/_overviews/FAQ/index.md
+++ b/_overviews/FAQ/index.md
@@ -362,14 +362,14 @@ setting in a multi-project build.
For example, if you add this to your `build.sbt`:
- scalaVersion := "2.13.17"
+ scalaVersion := "2.13.18"
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.17"
+ ThisBuild / scalaVersion := "2.13.18"
Other possibilities include:
diff --git a/_overviews/contribute/bug-reporting-guide.md b/_overviews/contribute/bug-reporting-guide.md
index 485a2994e1..5ccecd2137 100644
--- a/_overviews/contribute/bug-reporting-guide.md
+++ b/_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.17` 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.18` 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?
diff --git a/_overviews/core/binary-compatibility-of-scala-releases.md b/_overviews/core/binary-compatibility-of-scala-releases.md
index ba58a3482a..fb4de2be19 100644
--- a/_overviews/core/binary-compatibility-of-scala-releases.md
+++ b/_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., 17 in v2.13.17.
+For Scala 2, the *minor* version is the *third* number in a version, e.g., 18 in v2.13.18.
The major version is the second number, which is 13 in our example.
-Scala 2 up to 2.13.17 guarantees both backward and forward compatibility across *minor* releases within a single major release.
+Scala 2 up to 2.13.18 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.
diff --git a/_overviews/core/futures.md b/_overviews/core/futures.md
index 9f01a43710..b092d21172 100644
--- a/_overviews/core/futures.md
+++ b/_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 {
diff --git a/_overviews/jdk-compatibility/overview.md b/_overviews/jdk-compatibility/overview.md
index 2ffebe457c..77a17691dc 100644
--- a/_overviews/jdk-compatibility/overview.md
+++ b/_overviews/jdk-compatibility/overview.md
@@ -4,21 +4,46 @@ title: JDK Compatibility
permalink: /overviews/jdk-compatibility/overview.html
---
-Scala's primary platform is the Java Virtual Machine (JVM). (Other supported platforms: [Scala.js](https://www.scala-js.org/), [Scala Native](https://scala-native.org/).)
+Scala's primary platform is the Java Virtual Machine (JVM). Other supported platforms are [Scala.js](https://www.scala-js.org/) and [Scala Native](https://scala-native.org/).
Sometimes new JVM and JDK (Java Development Kit) versions require us to update Scala to remain compatible.
-## Scala compatibility table
+## Scala 3 compatibility
-Minimum Scala versions:
+Scala 3 versions from 3.3 LTS through Scala 3.7 support JDK 8 and above.
-| JDK | 3 | 3 LTS | 2.13 | 2.12 | 2.11 |
-|:-----------:|:--------:|:--------:|:---------:|:---------:|:----------:|
-| 25 (LTS) | 3.7.1 | 3.3.6 | 2.13.17 | 2.12.21* | |
-| 21 (LTS) | 3.4.0 | 3.3.1 | 2.13.11 | 2.12.18 | |
-| 17 (LTS) | 3.0.0 | 3.3.0 | 2.13.6 | 2.12.15 | |
-| 11 (LTS) | 3.0.0 | 3.3.0 | 2.13.0 | 2.12.4 | 2.11.12 |
-| 8 (LTS) | 3.0.0 | 3.3.0 | 2.13.0 | 2.12.0 | 2.11.0 |
+As per [this blog post](https://www.scala-lang.org/news/next-scala-lts-jdk.html),
+Scala 3.8 will have a new minimum JDK version of 17.
+
+The next Scala 3 LTS release will be Scala 3.9.
+
+Minimum Scala 3 versions for each JDK:
+
+| JDK | 3.8* | 3.4+ | 3.3 LTS |
+|:-----------:|:------:|:--------:|:--------:|
+| 25 (LTS) | 3.8.0* | 3.7.1 | 3.3.6 |
+| 21 (LTS) | 3.8.0* | 3.4.0 | 3.3.1 |
+| 17 (LTS) | 3.8.0* | 3.4.0 | 3.3.0 |
+| 11 (LTS) | | 3.4.0 | 3.3.0 |
+| 8 (LTS) | | 3.4.0 | 3.3.0 |
+
+\* = forthcoming; support available in [nightly builds](https://docs.scala-lang.org/overviews/core/nightlies.html)
+
+Even when a version combination isn't listed as supported, most features might still work.
+
+Using the latest patch version of your chosen Scala version line is always recommended.
+
+## Scala 2 compatibility
+
+Minimum Scala 2 versions for each JDK:
+
+| JDK | 2.13 | 2.12 |
+|:-----------:|:---------:|:---------:|
+| 25 (LTS) | 2.13.17 | 2.12.21* |
+| 21 (LTS) | 2.13.11 | 2.12.18 |
+| 17 (LTS) | 2.13.6 | 2.12.15 |
+| 11 (LTS) | 2.13.0 | 2.12.4 |
+| 8 (LTS) | 2.13.0 | 2.12.0 |
\* = forthcoming; support available in [nightly builds](https://docs.scala-lang.org/overviews/core/nightlies.html)
@@ -34,7 +59,7 @@ Minimum working versions:
| JDK | scala-cli | sbt | mill |
|:-----------:|:-----------:|:---------:|:-----------|
-| 25 (LTS) | forthcoming | 1.9.0 | 1.0.0 |
+| 25 (LTS) | 1.10.0 | 1.9.0 | 1.0.0 |
| 21 (LTS) | 1.0.0 | 1.9.0 | 0.11.5 |
| 17 (LTS) | 1.0.0 | 1.6.0 | 0.7.0 |
| 11 (LTS) | 1.0.0 | 1.1.0 | 0.1.5 |
@@ -50,11 +75,11 @@ Using a different build tool, such as Gradle or Maven? We invite pull requests a
## Running versus compiling
-JDK 8, 11, 17, 21, and 25 are all reasonable choices both for *compiling* and *running* Scala code.
+JDK 17, 21, and 25 are all good choices both for *compiling* and *running* Scala code.
-Since the JVM is normally backwards compatible, it is usually safe to use a newer JVM for *running* your code than the one it was compiled on, especially if you are not using JVM features designated "experimental" or "unsafe".
+JDK 8 and 11 are also possible choices. As of 2025, these versions remain in use at some shops, but usage has declined greatly and many projects are dropping support. If you compile on JDK 17+ but want to allow your users to stay on 8, use `--release 8` to avoid using APIs and features that don't exist in 8. Another option is to use a newer JDK for your daily work but do release builds on JDK 8.
-JDK 8 remains in use at some shops (as of 2023), but usage is declining and some projects are dropping support. If you compile on JDK 11+ but want to allow your users to stay on 8, additional care is needed to avoid using APIs and features that don't exist in 8. (For this reason, some Scala developers use a newer JDK for their daily work but do release builds on JDK 8.)
+Since the JVM is normally backwards compatible, it is usually safe to use a newer JVM for *running* your code than the one it was compiled on, especially if you are not using JVM features designated "experimental" or "unsafe".
As per [this blog post](https://www.scala-lang.org/news/next-scala-lts-jdk.html), Scala 3.8 will have a new minimum JDK version of 17.
@@ -74,15 +99,13 @@ In almost every case, you're free to use the JDK and JVM of your choice.
JDK 8 users typically use the Oracle JDK or some flavor of OpenJDK.
-Most JDK 11+ users are using OpenJDK, or GraalVM which runs in the context of OpenJDK. GraalVM performs well on the Scala benchmarks, and it benefits from GraalVM runtime and runs faster too.
-
OpenJDK comes in various flavors, offered by different providers. We typically build and test Scala using [Temurin](https://adoptium.net) or [Zulu](https://www.azul.com/downloads/), but the differences are unlikely to matter to most users.
## JDK 11 compatibility notes
The Scala test suite and Scala community build are green on JDK 11.
-In general, Scala works on JDK 11+, including GraalVM, but may not take special advantage of features that were added after JDK 8.
+In general, Scala works on JDK 11+, but may not take special advantage of features that were added after JDK 8.
For example, the Scala compiler does not enforce the restrictions of the Java Platform Module System, which means that code that typechecks may incur linkage errors at runtime. Scala 2.13.x will eventually provide [rudimentary support](https://github.com/scala/scala/pull/7218) for this (perhaps only in nightlies built on JDK 11).
@@ -132,8 +155,6 @@ For information on timing of the forthcoming release, see:
* https://contributors.scala-lang.org/t/scala-2-12-21-release-planning/6753
-
-
For possible Scala 3 issues, see the [area:jdk](https://github.com/scala/scala3/labels/area%3Ajdk) and [compat:java](https://github.com/scala/scala3/labels/compat%3Ajava) labels in [the Scala 3 issue tracker](https://github.com/scala/scala3/issues).
For possible Scala 2 issues, see the [jdk11](https://github.com/scala/bug/labels/jdk11), [jdk17](https://github.com/scala/bug/labels/jdk17), [jdk21](https://github.com/scala/bug/labels/jdk21), and [jdk25](https://github.com/scala/bug/labels/jdk25) labels in [the Scala 2 bug tracker](https://github.com/scala/bug/issues).
@@ -147,10 +168,3 @@ A few sbt plugins are offering support for GraalVM Native Image compilation:
- [sbt-native-packager](https://www.scala-sbt.org/sbt-native-packager/formats/graalvm-native-image.html)
- [sbt-native-image](https://github.com/scalameta/sbt-native-image)
-
-## Scala 3
-
-At present, both Scala 3.3 LTS and Scala Next support JDK 8, as well as 11 and beyond.
-
-As per [this blog post](https://www.scala-lang.org/news/next-scala-lts-jdk.html),
-Scala 3.8 will have a new minimum JDK version of 17. This can already be tested in Scala 3.8 nightlies.
diff --git a/_overviews/scala3-book/scala-for-python-devs.md b/_overviews/scala3-book/scala-for-python-devs.md
index c62c7f486c..ae4a18821c 100644
--- a/_overviews/scala3-book/scala-for-python-devs.md
+++ b/_overviews/scala3-book/scala-for-python-devs.md
@@ -40,7 +40,7 @@ At a high level, Scala shares these *similarities* with Python:
- Both have a relatively simple, concise syntax
- Both support a [functional style of programming][fp-intro]
- Both are object-oriented programming (OOP) languages
-- Both have comprehensions: Python has list comprehensions and Scala has `for` comprehensions
+- Both have comprehensions: Python has list comprehensions, dict comprehensions and generator expressions and Scala has `for` comprehensions
- Both languages have support for lambdas and [higher-order functions][hofs]
- Both can be used with [Apache Spark](https://spark.apache.org) for big data processing
- Both have a wealth of terrific libraries
@@ -693,6 +693,26 @@ Scala also has `match` expressions.
+### Lazily evaluated comprehensions:
+
+
+
+
+
+ from itertools import count
+
all_squares = (n**2 for n in count()) # generator expression
+
# all_squares: <generator object <genexpr> at ...>
+ |
+
+
+
+ val allSquares = for n <- LazyList.from(0) yield n * n
+
// allSquares: LazyList(<not computed>)
+ |
+
+
+
+
### `match` expressions:
diff --git a/_overviews/scala3-book/string-interpolation.md b/_overviews/scala3-book/string-interpolation.md
index 1ba335e3b7..968d49ecef 100644
--- a/_overviews/scala3-book/string-interpolation.md
+++ b/_overviews/scala3-book/string-interpolation.md
@@ -367,4 +367,4 @@ expansion, executing SQL queries, magic `$"identifier"` representations, and man
[java-format-docs]: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Formatter.html#detail
[value-class]: {% link _overviews/core/value-classes.md %}
-[sip-11]: {% link _sips/sips/string-interpolation.md %}
+[sip-11]: {% link _sips/sips/011-string-interpolation.md %}
diff --git a/_overviews/scala3-migration/tooling-scala2-xsource3.md b/_overviews/scala3-migration/tooling-scala2-xsource3.md
index ca23203026..e48b4c1205 100644
--- a/_overviews/scala3-migration/tooling-scala2-xsource3.md
+++ b/_overviews/scala3-migration/tooling-scala2-xsource3.md
@@ -125,7 +125,7 @@ class C(x: Int) {
### Changes affecting binary encoding
-As of Scala 2.13.17, there are 3 changes in `-Xsource-features` that affect binary encoding of classfiles:
+As of Scala 2.13.18, there are 3 changes in `-Xsource-features` that affect binary encoding of classfiles:
1. `case-apply-copy-access`: the constructor modifiers of case classes (`case class C private[p] (x: Int)`) are copied to the synthetic `apply` and `copy` methods.
1. `case-companion-function`: the synthetic companion objects of case classes no longer extend `FunctionN`.
diff --git a/_overviews/toolkit/http-client-request-body.md b/_overviews/toolkit/http-client-request-body.md
index b54357e1cb..2d39e08fc1 100644
--- a/_overviews/toolkit/http-client-request-body.md
+++ b/_overviews/toolkit/http-client-request-body.md
@@ -18,7 +18,7 @@ To send a POST request with a string body, you can chain `post` and `body` on a
import sttp.client4.quick._
val response = quickRequest
- .post(uri"https://example.com/")
+ .post(uri"https://httpbin.org/post")
.body("Lorem ipsum")
.send()
@@ -31,7 +31,7 @@ println(response.code)
import sttp.client4.quick.*
val response = quickRequest
- .post(uri"https://example.com/")
+ .post(uri"https://httpbin.org/post")
.body("Lorem ipsum")
.send()
@@ -51,7 +51,7 @@ The `body` method can also take a `Array[Byte]`, a `ByteBuffer` or an `InputStre
{% tab 'Scala 2 and 3' %}
```scala mdoc
val bytes: Array[Byte] = "john".getBytes
-val request = quickRequest.post(uri"https://example.com/").body(bytes)
+val request = quickRequest.post(uri"https://httpbin.org/post").body(bytes)
```
{% endtab %}
{% endtabs %}
diff --git a/_overviews/toolkit/http-client-what-else.md b/_overviews/toolkit/http-client-what-else.md
index c467c7687a..98557527ea 100644
--- a/_overviews/toolkit/http-client-what-else.md
+++ b/_overviews/toolkit/http-client-what-else.md
@@ -55,6 +55,7 @@ import scala.concurrent.{Await, Future}
import scala.concurrent.ExecutionContext.Implicits.global
import sttp.client4._
+import sttp.client4.ws.async._
import sttp.ws.WebSocket
val asyncBackend = DefaultFutureBackend()
@@ -83,6 +84,7 @@ import scala.concurrent.{Await, Future}
import scala.concurrent.ExecutionContext.Implicits.global
import sttp.client4.*
+import sttp.client4.ws.async.*
import sttp.ws.WebSocket
val asyncBackend = DefaultFutureBackend()
diff --git a/_overviews/tutorials/binary-compatibility-for-library-authors.md b/_overviews/tutorials/binary-compatibility-for-library-authors.md
index cb5807a068..cdfac174d1 100644
--- a/_overviews/tutorials/binary-compatibility-for-library-authors.md
+++ b/_overviews/tutorials/binary-compatibility-for-library-authors.md
@@ -255,7 +255,6 @@ alice match
Later in time, you can amend the original case class definition to, say, add an optional `address` field. You
* add a new field `address` and a custom `withAddress` method,
* update the public `apply` method in the companion object to initialize all the fields,
- * tell MiMa to [ignore](https://github.com/lightbend-labs/mima#filtering-binary-incompatibilities) changes to the class constructor. This step is necessary because MiMa does not yet ignore changes in private class constructor signatures (see [#738](https://github.com/lightbend-labs/mima/issues/738)).
{% tabs case_class_compat_4 class=tabs-scala-version %}
{% tab 'Scala 2' %}
@@ -284,28 +283,6 @@ object Person:
{% endtab %}
{% endtabs %}
-And, in your build definition:
-
-{% tabs case_class_compat_5 %}
-{% tab 'sbt' %}
-~~~ scala
-import com.typesafe.tools.mima.core._
-mimaBinaryIssueFilters += ProblemFilters.exclude[DirectMissingMethodProblem]("Person.this")
-~~~
-{% endtab %}
-{% endtabs %}
-
-Otherwise, MiMa would fail with an error like “method this(java.lang.String,Int)Unit in class Person does not have a correspondent in current version”.
-
-> Note that an alternative solution, instead of adding a MiMa exclusion filter, consists of adding back the previous
-> constructor signatures as secondary constructors:
-> ~~~ scala
-> case class Person private (name: String, age: Int, address: Option[String]):
-> ...
-> // Add back the former primary constructor signature
-> private[Person] def this(name: String, age: Int) = this(name, age, None)
-> ~~~
-
The original users can use the case class `Person` as before, all the methods that existed before are present unmodified after this change, thus the compatibility with the existing usage is maintained.
The new field `address` can be used as follows:
diff --git a/_ru/overviews/collections-2.13/iterators.md b/_ru/overviews/collections-2.13/iterators.md
index 3d43d76a8f..2c472e918f 100644
--- a/_ru/overviews/collections-2.13/iterators.md
+++ b/_ru/overviews/collections-2.13/iterators.md
@@ -177,7 +177,7 @@ language: ru
def zipWithIndex[A](i: Iterator[A]): Iterator[(Int, A)] =
Iterator.from(0).zip(i)
-### Буферезированные итераторы
+### Буферизированные итераторы
Иногда вам нужен итератор, который может "заглянуть вперед", чтобы вы могли оценить следующий элемент, который будет возвращен без перемещения позиции. Рассмотрим, например, задачу пропуска впереди идущих пустых строк из итератора, который возвращает последовательность строк. У вас может возникнуть соблазн написать следующее
diff --git a/_ru/scala3/book/string-interpolation.md b/_ru/scala3/book/string-interpolation.md
index 9e37b526fa..60e0770aea 100644
--- a/_ru/scala3/book/string-interpolation.md
+++ b/_ru/scala3/book/string-interpolation.md
@@ -410,4 +410,4 @@ p"${x/5}, $x" // Point(2.4, 12.0)
[java-format-docs]: https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Formatter.html#detail
[value-class]: {% link _overviews/core/value-classes.md %}
-[sip-11]: {% link _sips/sips/string-interpolation.md %}
+[sip-11]: {% link _sips/sips/011-string-interpolation.md %}
diff --git a/_sass/layout/cheatsheet.scss b/_sass/layout/cheatsheet.scss
index 691a34b38b..a9acf9a5db 100644
--- a/_sass/layout/cheatsheet.scss
+++ b/_sass/layout/cheatsheet.scss
@@ -4,7 +4,7 @@
.content-primary.cheatsheet {
code {
- font-family: 'Consolas';
+ font-family: 'Inconsolata';
}
pre.highlight {
diff --git a/_sass/layout/type-md.scss b/_sass/layout/type-md.scss
index 6548b1ff60..76b737d048 100755
--- a/_sass/layout/type-md.scss
+++ b/_sass/layout/type-md.scss
@@ -163,7 +163,7 @@
dt,
dd {
code {
- font-family: 'Consolas';
+ font-family: 'Inconsolata';
background-color: #fff;
color: #859900;
@include border-radius($border-radius-medium);
@@ -174,7 +174,7 @@
tr,
td{
code {
- font-family: 'Consolas';
+ font-family: 'Inconsolata';
font-size: 0.9375rem;
}
}
diff --git a/_sass/vendors/bourbon/addons/_font-stacks.scss b/_sass/vendors/bourbon/addons/_font-stacks.scss
index 57128f422a..351f5df5f2 100755
--- a/_sass/vendors/bourbon/addons/_font-stacks.scss
+++ b/_sass/vendors/bourbon/addons/_font-stacks.scss
@@ -22,7 +22,7 @@ $lucida-grande: "Lucida Grande", "Tahoma", "Verdana", "Arial", sans-serif;
///
/// @type List
-$monospace: "Bitstream Vera Sans Mono", "Consolas", "Courier", monospace;
+$monospace: "Bitstream Vera Sans Mono", "Inconsolata", "Courier", monospace;
/// Verdana font stack.
///
diff --git a/_sips/all.md b/_sips/all.md
index befff8ec61..19c649b9d3 100644
--- a/_sips/all.md
+++ b/_sips/all.md
@@ -2,47 +2,19 @@
layout: sips
title: List of All SIPs
-redirect_from:
+redirect_from:
- "/sips/sip-list.html"
- "/sips/pending/index.html"
---
-{% assign sips = site.sips | sort: title %}
+{% assign sips = site.sips | sort: 'number' | reverse %}
{% assign sipData = site.data.sip-data %}
-## Pre-SIP Discussions
-
-You can find so-called “pre-SIP discussions” in the Scala Contributors forum, under
-the category [Scala Improvement Process](https://contributors.scala-lang.org/c/sip/13).
-The goal of pre-SIP discussions is to gather initial community feedback and support.
-
## Pending SIPs
-Proposals that are at the design or implementation stage, and that are actively
-discussed by the committee and the proposals’ authors. Click on a proposal to
-read its content, or the corresponding discussions on GitHub if its design has
-not been accepted yet.
-
-
-
- {% for sip in sips %}
- {% if sip.stage == "design" or sip.stage == "implementation" %}
- -
-
-
- {{ sip.title }}
-
-
-
Stage: {{ sipData[sip.stage].text }}
- Status: {{ sipData[sip.status].text }}
- {% if sip.recommendation %}
- Recommendation: {{ sipData[sip.recommendation].text }}
- {% endif %}
-
- {% endif %}
- {% endfor %}
-
-
{{ sipData[sip.status].text }}
{% endif %}
- {% endfor %}
+ {% endfor %}
## Rejected SIPs
-Proposals that have been rejected by the committee. Click on a proposal to read the
-corresponding discussions on GitHub.
-
-
-
- {% for sip in sips %}
- {% if sip.status == "rejected" %}
- -
- {{ sip.title }}
-
- {% endif %}
- {% endfor %}
-
-
-
- {% for sip in sips %}
- {% if sip.status == "withdrawn" %}
- -
- {{ sip.title }}
-
- {% endif %}
- {% endfor %}
-
-