kotlin-fork/compiler/testData/diagnostics/tests/cyclicHierarchy/twoClassesWithNestedCycle.kt at 94de114894a6acdde75e3e0349b80c331aba6a67 - kotlin-fork - Azalea's Gitea

azalea/kotlin-fork

Files

T

Alexander Udalov cbe6e49a93 Consider outer classes when topsorting hierarchy

- when building a topsorted hierarchy, consider not only edges to the class'
  superclasses, but also from inner/nested classes to their container. This
  effectively means that a class cannot inherit from its nested class. Similar
  cases (see the tests) are disallowed in Java.
- filter classes by their presence in TopDownAnalysisContext, not by being a
  MutableClassDescriptor (otherwise analysis for local classes ends up trying
  to do something with outer superclasses)
- delete outdated comment: topsort is needed not only for better diagnostics,
  but also for correct order of fake overrides construction

2014-04-03 19:12:56 +04:00

7 lines

158 B

Kotlin

Vendored

Raw Blame History

 open class A : <!CYCLIC_INHERITANCE_HIERARCHY!>B.BB<!>() {
     open class AA
 }
 open class B : <!CYCLIC_INHERITANCE_HIERARCHY!>A.AA<!>() {
     open class BB
 }