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
24 lines
894 B
Kotlin
Vendored
24 lines
894 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: TestInitValInLambdaCalledOnce
|
|
// Public signature: /TestInitValInLambdaCalledOnce|null[0]
|
|
class TestInitValInLambdaCalledOnce {
|
|
// CHECK:
|
|
// Mangled name: TestInitValInLambdaCalledOnce{}x
|
|
// Public signature: /TestInitValInLambdaCalledOnce.x|-8060530855978347579[0]
|
|
val x: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: TestInitValInLambdaCalledOnce#<get-x>(){}kotlin.Int
|
|
// Public signature: /TestInitValInLambdaCalledOnce.x.<get-x>|4966956098150895696[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: TestInitValInLambdaCalledOnce#<get-x>(){}
|
|
// Public signature: /TestInitValInLambdaCalledOnce.x.<get-x>|1482705010654679335[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: TestInitValInLambdaCalledOnce#<init>(){}
|
|
// Public signature: /TestInitValInLambdaCalledOnce.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|