Better diagnosis for cyclic references caused by class clashes.

We now get a cyclic reference when inheriting from an inner class
with the same name in an outer supertype. Since this was legal
in Scala2 it's good to explain that particular case. Test case
in overrideClass.scala

1 files changed, 0 insertions, 19 deletions

diff --git a/tests/neg/overrides.scala b/tests/neg/overrides.scala
index 727759e3c..b7e598184 100644
--- a/tests/neg/overrides.scala
+++ b/tests/neg/overrides.scala
@@ -1,22 +1,3 @@
-  abstract class FooA {
-    type A <: Ax;
-    abstract class Ax;
-    abstract class InnerA {
-      type B <: A;
-      def doB : B;
-    }
-  }
-  trait FooB extends FooA {
-    type A <: Ax;
-    trait Ax extends super.Ax { def xxx : Int; } // error: classes cannot be overridden
-    abstract class InnerB extends InnerA {
-      // type B <: A;
-      val a : A = doB;
-      a.xxx;
-      doB.xxx;
-    }
-  }
-
 package p1 {
   abstract class T1 {
     protected def bug(p: Int = 1): Int // without 'protected' compiles fine