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
56 lines
874 B
Kotlin
Vendored
56 lines
874 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 TestEnum1 {
|
|
TEST1, TEST2
|
|
}
|
|
|
|
enum class TestEnum2(val x: Int) {
|
|
TEST1(1),
|
|
TEST2(2),
|
|
TEST3(3) {}
|
|
}
|
|
|
|
enum class TestEnum3 {
|
|
TEST {
|
|
override fun foo() {
|
|
println("Hello, world!")
|
|
}
|
|
}
|
|
;
|
|
abstract fun foo()
|
|
}
|
|
|
|
enum class TestEnum4(val x: Int) {
|
|
TEST1(1) {
|
|
override fun foo() {
|
|
println(TEST1)
|
|
}
|
|
},
|
|
TEST2(2) {
|
|
val z: Int
|
|
init {
|
|
z = x
|
|
}
|
|
override fun foo() {
|
|
println(TEST2)
|
|
}
|
|
}
|
|
;
|
|
abstract fun foo()
|
|
}
|
|
|
|
enum class TestEnum5(val x: Int = 0) {
|
|
TEST1, TEST2(), TEST3(0)
|
|
}
|
|
|
|
fun f(): Int = 1
|
|
|
|
enum class TestEnum6(val x: Int, val y: Int) {
|
|
TEST(y = f(), x = f())
|
|
}
|