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
32 lines
539 B
Kotlin
Vendored
32 lines
539 B
Kotlin
Vendored
// WITH_STDLIB
|
|
// IGNORE_BACKEND: JS_IR
|
|
// IGNORE_BACKEND: JS_IR_ES6
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57775, KT-57777
|
|
|
|
enum class Test0(val x: Int) {
|
|
ZERO;
|
|
constructor() : this(0)
|
|
}
|
|
|
|
enum class Test1(val x: Int) {
|
|
ZERO, ONE(1);
|
|
constructor() : this(0)
|
|
}
|
|
|
|
enum class Test2(val x: Int) {
|
|
ZERO {
|
|
override fun foo() {
|
|
println("ZERO")
|
|
}
|
|
},
|
|
ONE(1) {
|
|
override fun foo() {
|
|
println("ONE")
|
|
}
|
|
};
|
|
constructor() : this(0)
|
|
abstract fun foo()
|
|
}
|