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
21 lines
628 B
Kotlin
Vendored
21 lines
628 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: ModuleInfo
|
|
// Public signature: /ModuleInfo|null[0]
|
|
open annotation class ModuleInfo : Annotation {
|
|
// CHECK:
|
|
// Mangled name: ModuleInfo{}keyBind
|
|
// Public signature: /ModuleInfo.keyBind|-3946407517690370511[0]
|
|
val keyBind: Int
|
|
// CHECK JVM_IR:
|
|
// Mangled name: ModuleInfo#<get-keyBind>(){}kotlin.Int
|
|
// Public signature: /ModuleInfo.keyBind.<get-keyBind>|-5105783608349623557[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: ModuleInfo#<init>(kotlin.Int){}
|
|
// Public signature: /ModuleInfo.<init>|-5182794243525578284[0]
|
|
constructor(keyBind: Int) /* primary */
|
|
|
|
}
|
|
|