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
33 lines
718 B
Kotlin
Vendored
33 lines
718 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: Z
|
|
// Public signature: /Z|null[0]
|
|
object Z {
|
|
// CHECK:
|
|
// Mangled name: Z.A
|
|
// Public signature: /Z.A|null[0]
|
|
class A {
|
|
// CHECK:
|
|
// Mangled name: Z.A#<init>(){}
|
|
// Public signature: /Z.A.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
// CHECK:
|
|
// Mangled name: Z.A#test2(){}
|
|
// Public signature: /Z.A.test2|4279114864133353152[0]
|
|
fun test2(): Unit
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: Z#<init>(){}
|
|
// Public signature: /Z.<init>|-5645683436151566731[0]
|
|
private constructor() /* primary */
|
|
|
|
// CHECK:
|
|
// Mangled name: Z#test(){}
|
|
// Public signature: /Z.test|6620506149988718649[0]
|
|
fun test(): Unit
|
|
|
|
}
|
|
|