Fix issue with certain polyfunctions not properly matching in macros #23614
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
jchyb
force-pushed
the
fix-i23589-quoted-pattern
branch
from
53679ac to
55732ab
Compare
hamzaremmal
approved these changes
Jul 29, 2025
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.
Fixes #23589
previously the contents of TypeBoundsTree were directly compared with the types of defn.Nothing and defn.Any, which caused an issue where:
def.Nothing.tpeequalsTypeRef(ThisType(TypeRef(NoPrefix,module class scala)),class Nothing)TermRef(ThisType(TypeRef(NoPrefix,module class <root>)),object scala),Nothing)Same situation with the upper type bound
Any.isAnyandisNothingTypeaccept both types, so they are now used instead.