I am having a hard time explaining the difference in behavior between additional implicit values sought by either a primary implicit value or an implicit conversion. Specifically, this works:
trait Foo[A]
implicit def fooString: Foo[String] = null
implicit def value[A](implicit foo: Foo[A]) = 5
> implicitly[Int]
5
But this does not:
implicit def conversion[A](x: Int)(implicit foo: Foo[A]) = new {
def aMethod = 5
}
> 1.aMethod
could not find implicit value for parameter foo: test.Foo[A]
Varying:
implicitly
or an implicit conversionI get the following results:
Conversion/value Searching for Supplied | Works?
---------------- ------------- -------- | ------
conversion poly poly | yes
conversion poly mono | **no**
conversion mono poly | yes
conversion mono mono | yes
value poly poly | yes
value poly mono | yes
value mono poly | yes
value mono mono | yes
As you can see, the only case that does not work is when the search is started by an implicit conversion, the value sought is polymorphic, yet the value supplied is monomorphic.
Is there a theoretical reason why this should be the case, or is this a bug/limitation of Scala?
You're being bitten by scalac bug SI-3346. More generally see the description of SI-4699, esp. point (1),
1) implicit search and implicit conversion search treat undetermined type parameters differently
which you're observing directly where your cases are distinguishing between implicit values and implicit conversions.
I've updated SI-3346 to include this as an additional example.
Change the signature of the implicit conversion the following way:
implicit def conversion[A](a: A)(implicit foo: Foo[A]) = new {
Then call aMethod on a value of type for which an implicit value is defined, i.e. with a String:
scala> "foo".aMethod
res0: Int = 5
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With