Drop scala3-runtime, scala3-graal & scala3-graal-processor & deprecate pre-Scala-3.3 native images
#3929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #3922
What and why?
These modules have been used historically to handle issues with
sun.misc.Unsafe/ lazy val implementations in Scala 3.0-3.2.This is AFAIK no longer needed in modern Scala versions.
As pre-3.3 Scala is no longer supported, I am dropping those from the repository.
We still keep the dependency on old versions of those modules for the time being, just so that one could build native images with Scala 3.0-3.2, although that code path is deprecated for future removal.
Changes
scala3-runtimescala3-graalscala3-graal-processorPotential follow-ups
Were we to ever bump the internal JDK to 24 or higher, we'd need to remove this completely; for now, seems rather harmless to leave this as status quo.
We can consider removing it when we bump internal Scala to 3.9 - as far as I see it, Scala 3.0-3.2 is EOL, anyways. So perhaps sometime in 2026.
Further reading