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
Vendored
+2
-2
@@ -4,8 +4,8 @@ public fun foo(x: String?, y: String?): Int {
|
||||
// z is not null in both branches
|
||||
z.length
|
||||
// y is nullable if x != null
|
||||
y.<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
y.<!UNSAFE_CALL!>length<!>
|
||||
}
|
||||
// y is null because of the break
|
||||
return y.<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
return y.<!UNSAFE_CALL!>length<!>
|
||||
}
|
||||
Reference in New Issue
Block a user