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
36 lines
1.0 KiB
Kotlin
Vendored
36 lines
1.0 KiB
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: A
|
|
// Public signature: /A|null[0]
|
|
class A {
|
|
// CHECK:
|
|
// Mangled name: A{}test_1
|
|
// Public signature: /A.test_1|2561121963395013001[0]
|
|
val test_1: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: A#<get-test_1>(){}kotlin.Int
|
|
// Public signature: /A.test_1.<get-test_1>|-1575767838400056236[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: A#<get-test_1>(){}
|
|
// Public signature: /A.test_1.<get-test_1>|5475165570968103805[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: A{}test_2
|
|
// Public signature: /A.test_2|-375633585805266132[0]
|
|
val test_2: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: A#<get-test_2>(){}kotlin.Int
|
|
// Public signature: /A.test_2.<get-test_2>|1438436459582874026[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: A#<get-test_2>(){}
|
|
// Public signature: /A.test_2.<get-test_2>|-7104054319481711057[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: A#<init>(){}
|
|
// Public signature: /A.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|