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
14 lines
276 B
Kotlin
Vendored
14 lines
276 B
Kotlin
Vendored
// SKIP_SIGNATURE_DUMP
|
|
// ^ Difference in annotations generated by K1 and K2
|
|
|
|
annotation class Ann
|
|
|
|
interface IFoo {
|
|
@Ann val testVal: String
|
|
@Ann fun testFun()
|
|
@Ann val String.testExtVal: String
|
|
@Ann fun String.testExtFun()
|
|
}
|
|
|
|
class DFoo(d: IFoo) : IFoo by d
|