Skip to content

Backport "Upgrade to Scala.js 1.19.0." to 3.7 #23035

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 24, 2025

Conversation

tgodzik
Copy link
Contributor

@tgodzik tgodzik commented Apr 23, 2025

Backports #23026 to the 3.7.0-RC3.

PR submitted by the release tooling.

sjrd and others added 3 commits April 23, 2025 17:20
That is the commit that removed calls to `withStrictFloats(true)`,
which have been the default since 1.9.0, and cannot be changed
since 1.19.0.

[Cherry-picked bac43a7]
With minimal changes to preserve the status quo. These are forward
ports of compiler, library and build changes from the following
upstream commits:

* scala-js/scala-js@b38201c
  Drop support for non-strict floats.
* scala-js/scala-js@82910a0
  Move well-known names to a new object `WellKnownNames`.
* scala-js/scala-js@53dc4fe
  Introduce `NewLambda` to synthesize instances of SAM types.
* scala-js/scala-js@9481522
  Rewrite old IR with `AnonFunctionN` references to use `NewLambda`.

From the `NewLambda` commit, we only adapt the way we compile
Scala function lambdas. We do not use `NewLambda` for arbitrary
SAM types yet. This is left for a future, independent commit, as
it is not required for correctness.
With minimal changes to preserve the status quo. These are forward
ports of compiler, library and build changes from the following
upstream commits:

* scala-js/scala-js@b38201c
  Drop support for non-strict floats.
* scala-js/scala-js@82910a0
  Move well-known names to a new object `WellKnownNames`.
* scala-js/scala-js@53dc4fe
  Introduce `NewLambda` to synthesize instances of SAM types.
* scala-js/scala-js@9481522
  Rewrite old IR with `AnonFunctionN` references to use `NewLambda`.

From the `NewLambda` commit, we only adapt the way we compile
Scala function lambdas. We do not use `NewLambda` for arbitrary
SAM types yet. This is left for a future, independent commit, as
it is not required for correctness.

[Cherry-picked 12ca458][modified]
Copy link
Contributor

@WojciechMazur WojciechMazur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!
If we need a next RC anyway we can also consider adding JDK 25 support from #23004 Although this one can also be postponed to 3.7.1

@tgodzik tgodzik merged commit 9bdd736 into release-3.7.0 Apr 24, 2025
52 checks passed
@tgodzik tgodzik deleted the backport-release-3.7.0-23026 branch April 24, 2025 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants