You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.)
The text was updated successfully, but these errors were encountered:
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`
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.)
The text was updated successfully, but these errors were encountered: