Skip to content

Backport "Suggest imports for the expected type of the underlying implicit not found error" to LTS #19028

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
Merged
merged 1 commit into from
Dec 8, 2023
Merged

Backport "Suggest imports for the expected type of the underlying implicit not found error" to LTS #19028

merged 1 commit into from
Dec 8, 2023

Conversation

Kordyjan
Copy link
Contributor

Backports #17976 to the LTS branch.

PR submitted by the release tooling.
[skip ci]

@julienrf @Kordyjan
Suggest imports for the expected type of the underlying implicit not …
140d5db 
…found error

We used to suggest imports for the outermost type of a chain of implicits.
Now, we suggest imports for the `expectedType` of the underlying `NoMatchingImplicits`.

Fixes #8827

[Cherry-picked b614d84]
Base automatically changed from lts-17942 to release-3.3.2 December 8, 2023 15:16
@Kordyjan
Copy link
Contributor Author

Kordyjan commented Dec 8, 2023

No regressions detected in the community build up to lts-16941.

Reference

@Kordyjan Kordyjan merged commit c83442a into release-3.3.2 Dec 8, 2023
@Kordyjan Kordyjan deleted the lts-17976 branch December 8, 2023 15:16
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
@Kordyjan @julienrf