Alexander Udalov
9935519656
Use it in diagnostic tests with JVM backend instead of the
RENDER_DIAGNOSTICS_FULL_TEXT directive.
This is needed because otherwise in
AbstractDiagnosticsTestWithJvmBackend there are two handlers trying to
dump full diagnostic texts: JvmBackendDiagnosticsHandler and
FirDiagnosticsHandler, which dump different diagnostics (reported by
backend vs frontend) and in slightly different formats.
In fact, this is why exceptionFromInterpreter.fir.diag.txt was added in
48484368c7: the existing .diag.txt was detected as incorrect by
FirDiagnosticsHandler (even though the diagnostics are the same, just
printed in a different way), which led to the creation of .fir.diag.txt.
For these tests, the behavior about checking diagnostic text in
FirDiagnosticsHandler is useless because it doesn't include backend
diagnostics. So we disable it by using another directive.
13 lines
286 B
Kotlin
Vendored
13 lines
286 B
Kotlin
Vendored
// FIR_IDENTICAL
|
|
// !RENDER_ALL_DIAGNOSTICS_FULL_TEXT
|
|
|
|
inline fun inlineFun1(crossinline p: () -> Unit) {
|
|
object {
|
|
fun method() { <!INLINE_CALL_CYCLE!>inlineFun2(p)<!> }
|
|
}
|
|
}
|
|
|
|
inline fun inlineFun2(crossinline p: () -> Unit) {
|
|
<!INLINE_CALL_CYCLE!>inlineFun1(p)<!>
|
|
}
|