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
28 lines
781 B
Kotlin
Vendored
28 lines
781 B
Kotlin
Vendored
@file:A(x = "File annotation")
|
|
package test
|
|
|
|
// CHECK:
|
|
// Mangled name: test.A
|
|
// Public signature: test/A|null[0]
|
|
@Target(allowedTargets = [AnnotationTarget.FILE])
|
|
open annotation class A : Annotation {
|
|
// CHECK:
|
|
// Mangled name: test.A{}x
|
|
// Public signature: test/A.x|-8060530855978347579[0]
|
|
val x: String
|
|
// CHECK JVM_IR:
|
|
// Mangled name: test.A#<get-x>(){}kotlin.String
|
|
// Public signature: test/A.x.<get-x>|316111172223894646[0]
|
|
// CHECK JS_IR NATIVE:
|
|
// Mangled name: test.A#<get-x>(){}
|
|
// Public signature: test/A.x.<get-x>|1482705010654679335[0]
|
|
get
|
|
|
|
// CHECK:
|
|
// Mangled name: test.A#<init>(kotlin.String){}
|
|
// Public signature: test/A.<init>|1280618353163213788[0]
|
|
constructor(x: String) /* primary */
|
|
|
|
}
|
|
|