temp: fix testdata until diagnostic reporting is fixed properly
currently some old backend reporting schemes are used in IR backend that rely on the PSI alement passing. This conflicts with updated generic diagnostic infrastructure that is shared between FIR and IR backends. As soon as such places will be abstracted out and the IR will be completely switched to the new diagnostic infrastructure, this and similar changes could be reverted.
This commit is contained in:
+3
-3
@@ -4,10 +4,10 @@ compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/so
|
||||
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:14:13: error: a suspension point at SourceKt$test$2.invokeSuspend(source.kt:17) is inside a critical section
|
||||
builder {
|
||||
^
|
||||
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:49:1: error: a suspension point at SourceKt$test$3$invokeSuspend$$inlined$withCrossinline$2.invokeSuspend(source.kt:60) is inside a critical section
|
||||
inline fun withCrossinline(crossinline a: suspend () -> Unit): suspend () -> Unit {
|
||||
^
|
||||
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:50:34: error: a suspension point at SourceKt$withCrossinline$c$1.invokeSuspend(source.kt:52) is inside a critical section
|
||||
val c : suspend () -> Unit = {
|
||||
^
|
||||
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:49:1: error: a suspension point at SourceKt$test$3$invokeSuspend$$inlined$withCrossinline$2.invokeSuspend(source.kt:60) is inside a critical section
|
||||
inline fun withCrossinline(crossinline a: suspend () -> Unit): suspend () -> Unit {
|
||||
^
|
||||
COMPILATION_ERROR
|
||||
|
||||
Reference in New Issue
Block a user