-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Various compiler error messages still mention "implicit" #7710
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
Comments
While the keyword has changed, the current terminology is still |
we should use the suggestion given in this comment #9874 (comment) |
What is the conclusion here about the jargon we should use? Do we still use “implicit parameters”? Or do we now use “context parameters”? |
This changes some of the remaining messages that warn about "no implicit" to the new verbiage of "no given instance". fixes scala#7710
This changes some of the remaining messages that warn about "no implicit" to the new verbiage of "no given instance". fixes scala#7710
This changes some of the remaining messages that warn about "no implicit" to the new verbiage of "no given instance". fixes scala#7710
This changes some of the remaining messages that warn about "no implicit" to the new verbiage of "no given instance". fixes scala#7710
Uh oh!
There was an error while loading. Please reload this page.
Compiler Version
3.0.2
Minimised Code
Output
Expectation
Shouldn't the message mention "given"?
The text was updated successfully, but these errors were encountered: