We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
this came up in the context of Liszt:
object Test { class Foo(x: Meh) { def foo(a: String) = 1 } class Meh class A implicit object a extends A class B // implicit object b extends B implicit def mkFooA(x: Meh)(implicit w: A) : Foo = new Foo(x) implicit def mkFooB(x: Meh)(implicit w: B) : Foo = new Foo(x) (new Meh).foo("1") }
there should be no ambiguities as mkFooB requires an implicit value of type B, which is not available
The text was updated successfully, but these errors were encountered:
Imported From: https://issues.scala-lang.org/browse/SI-3340?orig=1 Reporter: @adriaanm
Sorry, something went wrong.
@adriaanm said: (In r21656) see #3340: tentative fix to resolve ambiguities by chasing transitively required implicits
@retronym said: Cool! We've worked around this limitation Scalaz, by splitting scalaz.MA into scalaz.MA / scalaz.MACofunctor.
#2781 is of the same ilk. Are you passing type constraints, too? I mean, they basically like extra implicit params of type <:<[A, B].
This works but implicit conversions are on the way out.
No branches or pull requests
this came up in the context of Liszt:
there should be no ambiguities as mkFooB requires an implicit value of type B, which is not available
The text was updated successfully, but these errors were encountered: