Imported From: https://issues.scala-lang.org/browse/SI-4805?orig=1
Reporter: DaveScala (davescala)
Affected Versions: 2.9.0
See #5211
Attachments:

• planets3.scala (created on Jul 14, 2011 4:18:55 PM UTC, 1457 bytes)
• planets5.scala (created on Jul 14, 2011 4:18:55 PM UTC, 1445 bytes)

Trond Olsen (tolsen77) said (edited on Aug 17, 2011 11:20:16 PM UTC):
Here is a simplified example of the looping implicit:
{noformat}class A
class B(val name: String) extends A
implicit def aToB(a: A): B = { println("aToB"); a }

println((new A).name)
// leads to infinite loop on implicit aToB()
{noformat}

Is this a programmer error, or should the typechecker make sure an implicit shouldn't be applicable within its own definition?

On second thought, it should fail completely. It's entirely nonsensical since a should never become a B, except the implicit is of a different opinion, hehe.

@soc said:
Verified on: 2.10.0.r26005-b20111114020239

@adriaanm said:
Yes, don't do that :-)