Files
kotlin-fork/compiler/testData/ir/irText/firProblems/OutBox.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

30 lines
781 B
Kotlin
Vendored

// CHECK:
// Mangled name: Box
// Public signature: /Box|null[0]
class Box<out T : Foo> {
// CHECK:
// Mangled name: Box{}foo
// Public signature: /Box.foo|1688079488202778848[0]
val foo: T
// CHECK JVM_IR:
// Mangled name: Box#<get-foo>(){}1:0
// Public signature: /Box.foo.<get-foo>|3855223738271342790[0]
get
// CHECK:
// Mangled name: Box#<init>(1:0){}
// Public signature: /Box.<init>|-8731461708390519279[0]
constructor(foo: T) /* primary */
// CHECK:
// Mangled name: Box{}str
// Public signature: /Box.str|4033248252607519654[0]
val str: String
// CHECK JVM_IR:
// Mangled name: Box#<get-str>(){}kotlin.String
// Public signature: /Box.str.<get-str>|7048381576567484853[0]
get(): String
}