Skip to content

Backport "Use more context for implicit search only if no default argument" to 3.7.3 #23713

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 3 commits into
base: release-3.7.3_backport-23702
Choose a base branch
from
Open

Backport "Use more context for implicit search only if no default argument" to 3.7.3 #23713

wants to merge 3 commits into from

Conversation

WojciechMazur
Copy link
Contributor

@WojciechMazur WojciechMazur commented Aug 11, 2025 •
edited
Loading

Backports #23664 to the 3.7.3-RC2.

PR submitted by the release tooling.
[skip ci]

odersky added 3 commits August 11, 2025 22:27
@odersky @WojciechMazur
More careful ClassTag instantiation
61d0073 
We now use a blend of the new scheme and backwards compatible special case if type variables
as ClassTag arguments are constrained by further type variables.

Fixes #23611

[Cherry-picked b677f97]
@odersky @WojciechMazur
Refine criterion when to use fullyDefinedType in ClassTag search
c31e1b7 
[Cherry-picked e4b8f3c]
@odersky @WojciechMazur
Use more context for implicit search only if no default argument
4dd0691 
After an "implicit not found", we type additional arguments to get more context which might
give a larger implicit scope to search. With this commit we do that only if there is no
default argument for the implicit.

This might fix #23610

[Cherry-picked 975c988]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@WojciechMazur @odersky