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
793 B
Kotlin
Vendored
25 lines
793 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: {}test
|
|
// Public signature: /test|-5712650070209114719[0]
|
|
val test: String
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-test>(){}kotlin.String
|
|
// Public signature: /test.<get-test>|-8411936358597690329[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-test>(){}
|
|
// Public signature: /test.<get-test>|208282462577758837[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: @0:0{0§<kotlin.Any?>}id
|
|
// Public signature: /id|6409895071901545951[0]
|
|
val <T : Any?> T.id: T
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-id>@0:0(){0§<kotlin.Any?>}0:0
|
|
// Public signature: /id.<get-id>|4983271234253098452[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-id>@0:0(){0§<kotlin.Any?>}
|
|
// Public signature: /id.<get-id>|-1537502770664138716[0]
|
|
get(): T
|
|
|