Repository navigation
Conversation
Scala 3.3.8 allows to opt in to the lazy val encoding Scala 3.8+ uses to avoid warnings/errors on JVM 25+. As we already bumped the minimum JDK version to 17, the fact that future lazy vals require 9+ is no problem. On the positive side, we avoid our users getting annoyed (or having to resort to bytecode manipulation via VirtusLab/sloth) when using JVM 25 or higher.
Collaborator
Author
|
Merged #803 instead. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scala 3.3.8 allows to opt in to the lazy val encoding Scala 3.8+ uses to avoid warnings/errors on JVM 25+. As we already bumped the minimum JDK version to 17, the fact that future lazy vals require 9+ is no problem. On the positive side, we avoid our users getting annoyed (or having to resort to bytecode manipulation via VirtusLab/sloth) when using JVM 25 or higher.
#805 brings the same encoding for
scala-xml, so we should merge these two together. Alternatively, we could merge #803 and go straight to Scala 3.9, the new LTS which has the future lazy vals on by default. It was released only recently though and I think we don't have strong enough justification to make the bump just yet – nobody really profits, but some users may run into problems.