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
29 lines
837 B
Kotlin
Vendored
29 lines
837 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: {}p
|
|
// Public signature: /p|6715504260787941082[0]
|
|
val p: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-p>(){}kotlin.Int
|
|
// Public signature: /p.<get-p>|5329635969197638839[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #<get-p>(){}
|
|
// Public signature: /p.<get-p>|-1162552463316289847[0]
|
|
get
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #foo(){}kotlin.Int
|
|
// Public signature: /foo|-1256155405684507276[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #foo(){}
|
|
// Public signature: /foo|-1041209573719867811[0]
|
|
fun foo(): Int
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #test(kotlin.IntArray){}kotlin.Int
|
|
// Public signature: /test|3593442840675733055[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: #test(kotlin.IntArray){}
|
|
// Public signature: /test|7529327046024896503[0]
|
|
fun test(a: IntArray): Int
|
|
|