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
403 B
Kotlin
Vendored
17 lines
403 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: Owner
|
|
// Public signature: /Owner|null[0]
|
|
class Owner {
|
|
// CHECK:
|
|
// Mangled name: Owner#<init>(){}
|
|
// Public signature: /Owner.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
// CHECK:
|
|
// Mangled name: Owner#foo(0:0;0:0){0§<kotlin.Any?>}
|
|
// Public signature: /Owner.foo|6541897014956795195[0]
|
|
fun <T : Any?> foo(x: T, y: T): Unit
|
|
|
|
}
|
|
|