Skip to content
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.

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

Don't issue implicit errors if parameter has default value #14849

Merged
merged 2 commits into from Apr 5, 2022

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Apr 5, 2022

If implicit parameters have default values then we try to re-type the
application with default values supplied as arguments. So far we
fell back to the original errors if retyping failed, which can lead
to confusing error messages. We now stick with the retyping in all cases.

Fixes #14842

If implicit parameters have default values then we try to re-type the
application with default values supplied as arguments. So far we
fell back to the original errors if retyping failed, which can lead
to confusing error messages. We now stick with the retyping in all cases.

Fixes scala#14842
@odersky odersky merged commit 0fca562 into scala:main Apr 5, 2022
@odersky odersky deleted the fix-14842 branch April 5, 2022 12:44
@Kordyjan Kordyjan added this to the 3.1.3 milestone Aug 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Misleading error message with default given parameter
2 participants