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

Unify implicitNotFound and regular string interpolation #7411

Open
scabug opened this issue Apr 23, 2013 · 2 comments
Open

Unify implicitNotFound and regular string interpolation #7411

scabug opened this issue Apr 23, 2013 · 2 comments
Labels
Milestone

Comments

@scabug
Copy link

scabug commented Apr 23, 2013

Having all these annotations running around with interpolated-strings-which-aren't does not feel good. @implicitNotFound should be "reimagined" in some form which is consistent with string interpolation. In fact one could take the opportunity to generalize it properly so that creating better error messages based on interpolating annotation arguments and elements of the enclosing scope could be used by anyone who cared to.

Because right now it's just a little bundle of maintenance (see "object ImplicitNotFoundMsg" in implicits.)

@scabug
Copy link
Author

scabug commented Apr 23, 2013

Imported From: https://issues.scala-lang.org/browse/SI-7411?orig=1
Reporter: @paulp

@som-snytt
Copy link

tpolecat would care to craft a better message:

I have a nice setup but FQNs fq with it `Operation doobie.labs.qb.hidden.StateMachine.Having isn't permitted here. Allowed: doobie.labs.qb.hidden.StateMachine.Join with doobie.labs.qb.hidden.StateMachine.Where with doobie.labs.qb.hidden.StateMachine.Select`

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants