-
Notifications
You must be signed in to change notification settings - Fork 1.1k
confusing Implicit parameters should be provided with a using clause
message if implicit default param
#22567
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
Labels
area:reporting
Error reporting including formatting, implicit suggestions, etc
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:enhancement
Comments
2 tasks
unnecessary Scala 2 cross build. here is more simple example
|
The tricky bit (IIRC) is that Scala 2 does not honor default args if implicits are supplied implicitly; that is a Scala 3 innovation. |
hamzaremmal
added a commit
to hamzaremmal/scala3
that referenced
this issue
Mar 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:reporting
Error reporting including formatting, implicit suggestions, etc
better-errors
Issues concerned with improving confusing/unhelpful diagnostic messages
itype:enhancement
Compiler version
3.7.0-RC1-bin-20250207-d60a914-NIGHTLY
Minimized example
a1/src/main/scala/A1.scala
a2/src/main/scala/A2.scala
build.sbt
Output Error/Warning message
Why this Error/Warning was not helpful
This is implicit params but not call with explicit.
Suggested improvement
Note
The text was updated successfully, but these errors were encountered: