FIR checker: differentiate UNSAFE_CALL from INAPPLICABLE_CANDIDATE
To do so, inside the root cause of inapplicable candidate errors, we will record expected/actual type of receiver, if any. That will help identifying inapplicable calls on nullable receiver.
This commit is contained in:
committed by
Mikhail Glukhikh
parent
4b823eca21
commit
e72ddbcbfe
+2
-2
@@ -27,11 +27,11 @@ fun testUnsafeCaptureVarInInitializer() {
|
||||
|
||||
val s = when (val y = run { x = null; 32 }) {
|
||||
0 -> {
|
||||
x.<!INAPPLICABLE_CANDIDATE!>inc<!>() // NB smart cast should be impossible
|
||||
x.<!UNSAFE_CALL!>inc<!>() // NB smart cast should be impossible
|
||||
"0"
|
||||
}
|
||||
else -> "!= 0"
|
||||
}
|
||||
|
||||
x.<!INAPPLICABLE_CANDIDATE!>inc<!>() // NB smart cast should be impossible
|
||||
x.<!UNSAFE_CALL!>inc<!>() // NB smart cast should be impossible
|
||||
}
|
||||
Reference in New Issue
Block a user