Dmitry Petrov
5d9ee7efee
- base class method wins against a (default) interface method, so an abstract base class method should always be implemented in a derived class; - interface methods clash regardless of abstract/default with possibly undefined behavior at run-time, so a class or interface should always define its own method for methods inherited from multiple interfaces and not from base class; - meaningful diagnostics for class inheriting conflicting JVM signatures. Since no override will happen under Java 8 rules, ACCIDENTAL_OVERRIDE is misleading for this case; - update testData.
30 lines
573 B
Kotlin
Vendored
30 lines
573 B
Kotlin
Vendored
//KT-559 Forbid abstract method call through super
|
|
|
|
package kt559
|
|
|
|
abstract class A {
|
|
abstract val i : Int
|
|
|
|
abstract fun foo() : Int
|
|
|
|
fun fff() {}
|
|
}
|
|
|
|
abstract class D(): A() {
|
|
override val i : Int = 34
|
|
}
|
|
|
|
<!ABSTRACT_CLASS_MEMBER_NOT_IMPLEMENTED!>class C<!>() : D() {
|
|
fun test() {
|
|
super.i
|
|
}
|
|
}
|
|
|
|
<!ABSTRACT_CLASS_MEMBER_NOT_IMPLEMENTED!>class B<!>() : A() {
|
|
override fun foo(): Int {
|
|
super.<!ABSTRACT_SUPER_CALL!>i<!>
|
|
|
|
super.fff() //everything is ok
|
|
return super.<!ABSTRACT_SUPER_CALL!>foo<!>() //no error!!
|
|
}
|
|
} |