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

31 lines
748 B
Kotlin
Vendored

// CHECK:
// Mangled name: Base
// Public signature: /Base|null[0]
open class Base {
// CHECK:
// Mangled name: Base#<init>(){}
// Public signature: /Base.<init>|-5645683436151566731[0]
constructor() /* primary */
}
// CHECK:
// Mangled name: Test
// Public signature: /Test|null[0]
class Test : Base {
// CHECK:
// Mangled name: Test#<init>(){}
// Public signature: /Test.<init>|-5645683436151566731[0]
constructor()
// CHECK:
// Mangled name: Test#<init>(kotlin.Int){}
// Public signature: /Test.<init>|-5182794243525578284[0]
constructor(xx: Int)
// CHECK:
// Mangled name: Test#<init>(kotlin.Short){}
// Public signature: /Test.<init>|-8537285994488541433[0]
constructor(xx: Short)
}