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
18 lines
347 B
Kotlin
Vendored
18 lines
347 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: IFoo
|
|
// Public signature: /IFoo|null[0]
|
|
interface IFoo {
|
|
|
|
// CHECK:
|
|
// Mangled name: IFoo#bar(){}
|
|
// Public signature: /IFoo.bar|496682602797471549[0]
|
|
fun bar(): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: IFoo#foo(){}
|
|
// Public signature: /IFoo.foo|-1041209573719867811[0]
|
|
abstract fun foo(): Unit
|
|
|
|
}
|
|
|