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
23 lines
526 B
Kotlin
Vendored
23 lines
526 B
Kotlin
Vendored
// TARGET_BACKEND: JVM
|
|
// WITH_STDLIB
|
|
// FULL_JDK
|
|
|
|
// MUTE_SIGNATURE_COMPARISON_K2: ANY
|
|
// ^ KT-57778
|
|
|
|
import java.io.Reader
|
|
import java.io.StringReader
|
|
|
|
private const val BACKSLASH = '\\'
|
|
|
|
private fun Reader.nextChar(): Char? =
|
|
read().takeUnless { it == -1 }?.toChar()
|
|
|
|
fun Reader.consumeRestOfQuotedSequence(sb: StringBuilder, quote: Char) {
|
|
var ch = nextChar()
|
|
while (ch != null && ch != quote) {
|
|
if (ch == BACKSLASH) nextChar()?.let { sb.append(it) } else sb.append(ch)
|
|
ch = nextChar()
|
|
}
|
|
}
|