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
17 lines
388 B
Kotlin
Vendored
17 lines
388 B
Kotlin
Vendored
@file:JvmName(name = "FileWithAnnotations")
|
|
|
|
// CHECK:
|
|
// Mangled name: {}bar
|
|
// Public signature: /bar|-7864284097863469857[0]
|
|
val bar: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #<get-bar>(){}kotlin.Int
|
|
// Public signature: /bar.<get-bar>|-7403724005139201014[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: #foo(){}
|
|
// Public signature: /foo|-1041209573719867811[0]
|
|
fun foo(): Unit
|
|
|