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
13 lines
307 B
Kotlin
Vendored
13 lines
307 B
Kotlin
Vendored
// SKIP_SIGNATURE_DUMP
|
|
// ^ K1 generates a useless delegate field for the Test2 class, K2 does not
|
|
|
|
interface IBase<A> {
|
|
fun <B> foo(a: A, b: B)
|
|
val <C> C.id: Map<A, C>?
|
|
var <D> List<D>.x: D?
|
|
}
|
|
|
|
class Test1<E>(i: IBase<E>) : IBase<E> by i
|
|
|
|
class Test2(var j: IBase<String>) : IBase<String> by j
|