chore: deprecate the content of the scala.runtime.stdLibPatches package
#24587
+9
−6
Conversation
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
hamzaremmal
commented
Nov 28, 2025
| /** Scala 3 additions and replacements to the `scala.language` object. */ | ||
| @publicInBinary | ||
| @deprecated(message = "Patches are not applied to the stdlib anymore", since = "3.8.0") | ||
| private[scala] object language: |
Member
Author
There was a problem hiding this comment.
Consulting @sjrd for a second opinion. This should be fine since the TASTy should have symbols to the real ones that we used to patch, not the fake ones. The only reason it would break is if people refer directly to them in their source code (then, it is on them).
hamzaremmal
force-pushed
the
deprecated-patches
branch
from
69c2e8f to
59875eb
Compare
hamzaremmal
added
the
backport:nominated
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Since I'm blocked by a bug in #24477, lets at least deprecate the objects not allow access to them anymore for 3.8.0.