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
28 lines
516 B
Kotlin
Vendored
28 lines
516 B
Kotlin
Vendored
// TARGET_BACKEND: JVM_IR
|
|
// DUMP_LOCAL_DECLARATION_SIGNATURES
|
|
// SKIP_KLIB_TEST
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57430
|
|
|
|
// FILE: Collector.java
|
|
|
|
public class Collector {
|
|
public void flush() {}
|
|
}
|
|
|
|
// FILE: FlushFromAnonymous.kt
|
|
|
|
class Serializer() {
|
|
fun serialize() {
|
|
val messageCollector = createMessageCollector()
|
|
try {
|
|
|
|
} catch (e: Throwable) {
|
|
messageCollector.flush()
|
|
}
|
|
}
|
|
|
|
private fun createMessageCollector() = object : Collector() {}
|
|
}
|