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
24 lines
501 B
Kotlin
Vendored
24 lines
501 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: SomeAnn
|
|
// Public signature: /SomeAnn|null[0]
|
|
open annotation class SomeAnn : Annotation {
|
|
// CHECK:
|
|
// Mangled name: SomeAnn#<init>(){}
|
|
// Public signature: /SomeAnn.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: My
|
|
// Public signature: /My|null[0]
|
|
@SomeAnn
|
|
class My {
|
|
// CHECK:
|
|
// Mangled name: My#<init>(){}
|
|
// Public signature: /My.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|