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
28 lines
438 B
Kotlin
Vendored
28 lines
438 B
Kotlin
Vendored
// IGNORE_BACKEND: JS_IR
|
|
// IGNORE_BACKEND: JS_IR_ES6
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57777
|
|
|
|
annotation class TestAnn(val x: String)
|
|
|
|
@TestAnn("class")
|
|
class TestClass
|
|
|
|
@TestAnn("interface")
|
|
interface TestInterface
|
|
|
|
@TestAnn("object")
|
|
object TestObject
|
|
|
|
class Host {
|
|
@TestAnn("companion")
|
|
companion object TestCompanion
|
|
}
|
|
|
|
@TestAnn("enum")
|
|
enum class TestEnum
|
|
|
|
@TestAnn("annotation")
|
|
annotation class TestAnnotation
|