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
19 lines
412 B
Kotlin
Vendored
19 lines
412 B
Kotlin
Vendored
// CHECK:
|
|
// Mangled name: #test1(){}
|
|
// Public signature: /test1|4297044443957252634[0]
|
|
@JavaAnn
|
|
fun test1(): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #test2(){}
|
|
// Public signature: /test2|4279114864133353152[0]
|
|
@JavaAnn(value = "abc", i = 123)
|
|
fun test2(): Unit
|
|
|
|
// CHECK:
|
|
// Mangled name: #test3(){}
|
|
// Public signature: /test3|-3759735065270951803[0]
|
|
@JavaAnn(value = "abc", i = 123)
|
|
fun test3(): Unit
|
|
|