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
25 lines
815 B
Kotlin
Vendored
25 lines
815 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: {}test1
|
|
// Public signature: /test1|6005685442305498193[0]
|
|
val test1: Function0<Int>
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-test1>(){}kotlin.Function0<kotlin.Int>
|
|
// Public signature: /test1.<get-test1>|3140014614812373095[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-test1>(){}
|
|
// Public signature: /test1.<get-test1>|-5735092642142423279[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: {}test2
|
|
// Public signature: /test2|2517758057000911509[0]
|
|
val test2: Function0<Unit>
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-test2>(){}kotlin.Function0<kotlin.Unit>
|
|
// Public signature: /test2.<get-test2>|-6581063117552766488[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-test2>(){}
|
|
// Public signature: /test2.<get-test2>|-5218942532816206869[0]
|
|
get
|
|
|