surface (internal): Use .typeMember instead of .tree to get parameter types #3466
Conversation
This file contains 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
OndrejSpanel
force-pushed
the
i3417-avoid-tree
branch
from
7304194 to
e9189f5
Compare
OndrejSpanel
force-pushed
the
i3417-avoid-tree
branch
from
e9189f5 to
2774c3e
Compare
OndrejSpanel
force-pushed
the
i3417-avoid-tree
branch
from
a6b5ed8 to
4a8d185
Compare
xerial
changed the title
|
Thanks for the improvement. Merged |
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.
Do not use
.treeto obtain parameter types, usetypeMemberinstead. The code is simpler and more reliable, avoiding issue scala/scala3#19795 (#3417)