Files
kotlin-fork/compiler/testData/ir/irText/declarations/annotations/constructorsWithAnnotations.sig.kt.txt
T
Sergej Jaskiewicz 6e8283a6fe [IR] Dump IdSignatures and mangled names in irText tests
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
2023-05-15 18:20:45 +00:00

41 lines
1.1 KiB
Kotlin
Vendored

// CHECK:
// Mangled name: TestAnn
// Public signature: /TestAnn|null[0]
open annotation class TestAnn : Annotation {
// CHECK:
// Mangled name: TestAnn{}x
// Public signature: /TestAnn.x|-8060530855978347579[0]
val x: Int
// CHECK JVM_IR:
// Mangled name: TestAnn#<get-x>(){}kotlin.Int
// Public signature: /TestAnn.x.<get-x>|4966956098150895696[0]
// CHECK JS_IR NATIVE:
// Mangled name: TestAnn#<get-x>(){}
// Public signature: /TestAnn.x.<get-x>|1482705010654679335[0]
get
// CHECK:
// Mangled name: TestAnn#<init>(kotlin.Int){}
// Public signature: /TestAnn.<init>|-5182794243525578284[0]
constructor(x: Int) /* primary */
}
// CHECK:
// Mangled name: TestClass
// Public signature: /TestClass|null[0]
class TestClass {
// CHECK:
// Mangled name: TestClass#<init>(){}
// Public signature: /TestClass.<init>|-5645683436151566731[0]
@TestAnn(x = 1)
constructor() /* primary */
// CHECK:
// Mangled name: TestClass#<init>(kotlin.Int){}
// Public signature: /TestClass.<init>|-5182794243525578284[0]
@TestAnn(x = 2)
constructor(x: Int)
}