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
30 lines
544 B
Kotlin
Vendored
30 lines
544 B
Kotlin
Vendored
// IGNORE_BACKEND_K1: JS_IR
|
|
// IGNORE_BACKEND_K1: JS_IR_ES6
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57429
|
|
|
|
// MODULE: m1
|
|
// FILE: genericClassInDifferentModule_m1.kt
|
|
|
|
abstract class Base<T>(val x: T) {
|
|
abstract fun <Y> foo(y: Y): T
|
|
|
|
abstract var bar: T
|
|
|
|
abstract var <Z> Z.exn: T
|
|
}
|
|
|
|
// MODULE: m2(m1)
|
|
// FILE: genericClassInDifferentModule_m2.kt
|
|
|
|
class Derived1<T>(x: T) : Base<T>(x) {
|
|
override fun <Y> foo(y: Y): T = x
|
|
|
|
override var bar: T = x
|
|
|
|
override var <Z> Z.exn: T
|
|
get() = x
|
|
set(value) {}
|
|
}
|