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
It seems that, when dealing with implicit resolution, the order of definition of classes and companion object matters. The minimal example I was able to cook up is:
@adriaanm said (edited on Oct 15, 2012 2:26:08 PM UTC):
I'm not sure this is going to be easy to fix or even whether it should. Assigning to meeting for input.
It seems that, when dealing with implicit resolution, the order of definition of classes and companion object matters. The minimal example I was able to cook up is:
This fails to compile saying "could not find implicit value for parameter c: Counter[Bar]"
On the other hand, if we define object Bar before case class Bar, it compiles fine.
I should also mention that this problem only arises with implicit resolution. If we explicitly pass the BarCounter object, everything compiles fine.
The text was updated successfully, but these errors were encountered: