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
20 lines
449 B
Kotlin
Vendored
20 lines
449 B
Kotlin
Vendored
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57429, KT-57436
|
|
|
|
open class L<LL>(val ll: LL)
|
|
|
|
class Rec<T>(val rt: T)
|
|
|
|
val <PT> Rec<PT>.p: L<PT>
|
|
get() {
|
|
class PLocal<LT>(lt: LT, val pt: PT): L<LT>(lt)
|
|
return foo2(rt, rt, ::PLocal)
|
|
}
|
|
|
|
fun <FT> Rec<FT>.fn(): L<FT> {
|
|
class FLocal<LT>(lt: LT, val pt: FT) : L<LT>(lt)
|
|
return foo2(rt, rt, ::FLocal)
|
|
}
|
|
|
|
fun <T1, T2, R> foo2(t1: T1, t2: T2, bb: (T1, T2) -> R): R = bb(t1, t2)
|