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
+1
-1
@@ -14,7 +14,7 @@ class MyClass {
|
||||
var res = 0
|
||||
m = create()
|
||||
// See KT-7428
|
||||
<!INAPPLICABLE_CANDIDATE!>for ((k, v) in m)
|
||||
<!UNSAFE_CALL!>for ((k, v) in m)
|
||||
res += (k.length + v.length)<!>
|
||||
return res
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user