Sergej Jaskiewicz
6e8283a6fe
The reason #1 for this feature is that we want to test IdSignatures generated for declarations. Currently, there is no (easy) way to ensure that a change in the signature building logic doesn't cause any breaking changes wrt klibs. Now, most IdSignatures include hashed mangled names in them, so even if we catch a regression where the included hash changes, there would be no way of knowing immediately what caused it, unless we'd also have mangled names in the expectations. The reason #2 is to test the manglers themselves. Currently, there are no tests for them. They heavily duplicate each other, this is already causing issues (see KT-57427) that would be very hard to catch without these tests. ^KT-58238 Fixed
31 lines
512 B
Kotlin
Vendored
31 lines
512 B
Kotlin
Vendored
// TARGET_BACKEND: JVM
|
|
// SKIP_KT_DUMP
|
|
// DUMP_EXTERNAL_CLASS: X
|
|
// DUMP_EXTERNAL_CLASS: AX
|
|
|
|
// SKIP_SIGNATURE_DUMP
|
|
// ^ Fake overrides have divirging @EnhancedNullability in K1 and K2
|
|
|
|
// FILE: kt45853.kt
|
|
|
|
abstract class A {
|
|
abstract val a: A?
|
|
}
|
|
|
|
class B() : AX() {
|
|
override fun getA(): X? = super.a
|
|
}
|
|
|
|
// FILE: X.java
|
|
public interface X {
|
|
X getA();
|
|
}
|
|
|
|
// FILE: AX.java
|
|
public abstract class AX extends A implements X {
|
|
@Override
|
|
public AX getA() {
|
|
return (AX) super.getA();
|
|
}
|
|
}
|