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
22 lines
546 B
Kotlin
Vendored
22 lines
546 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: A
|
|
// Public signature: /A|null[0]
|
|
class A {
|
|
// CHECK:
|
|
// Mangled name: A#<init>(){}
|
|
// Public signature: /A.<init>|-5645683436151566731[0]
|
|
constructor() /* primary */
|
|
|
|
}
|
|
|
|
// CHECK:
|
|
// Mangled name: #set@A(kotlin.IntArray...;kotlin.Int){}
|
|
// Public signature: /set|-7344305741500909935[0]
|
|
operator fun A.set(vararg i: Int, v: Int): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #testSimpleAssignment(A){}
|
|
// Public signature: /testSimpleAssignment|1100548656282165605[0]
|
|
fun testSimpleAssignment(a: A): Unit
|
|
|