Ilmir Usmanov
281f09f077
There is a trade-off between robustness of check and accuracy of the diagnostic: the previous version, which works on generation, was too fragile and lead to false-positives. Now we check on state machine generation. However, since we do not have PSI for call, we can only report diagnostic on whole suspend function or suspend lambda. Additionally, the state machine is generated on crossinline suspend lambdas regeneration and thus we do not have the PSI for the lambda as well! #KT-27130 Fixed #KT-27258 Open
14 lines
747 B
Plaintext
Vendored
14 lines
747 B
Plaintext
Vendored
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:8:13: error: a suspension point is inside a critical section
|
|
builder {
|
|
^
|
|
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:14:13: error: a suspension point is inside a critical section
|
|
builder {
|
|
^
|
|
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:20:13: error: a suspension point is inside a critical section
|
|
builder {
|
|
^
|
|
compiler/testData/compileKotlinAgainstCustomBinaries/suspensionPointInMonitor/source.kt:42:9: error: a suspension point is inside a critical section
|
|
override suspend fun run() {
|
|
^
|
|
COMPILATION_ERROR
|