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
599 B
Kotlin
Vendored
29 lines
599 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: Ann
|
|
// Public signature: /Ann|null[0]
|
|
open annotation class Ann : Annotation {
|
|
// CHECK:
|
|
// Mangled name: Ann#<init>(){}
|
|
// Public signature: /Ann.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: I
|
|
// Public signature: /I|null[0]
|
|
interface I {
|
|
|
|
// CHECK:
|
|
// Mangled name: I#m(kotlin.String){}
|
|
// Public signature: /I.m|934693771674457301[0]
|
|
fun m(@Ann s: String): Unit
|
|
|
|
}
|
|
|
|
// CHECK JVM_IR:
|
|
// Mangled name: #box(){}kotlin.String
|
|
// Public signature: /box|-9347091776561469[0]
|
|
fun box(): String
|
|
|