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
@@ -36,6 +36,6 @@ fun foo(x: Iterator<String>, y: Iterator<String?>) {
|
||||
|
||||
x.forEachRemaining { it -> it.length }
|
||||
x.forEachRemaining { it -> it?.length }
|
||||
y.forEachRemaining { it -> it.<!INAPPLICABLE_CANDIDATE!>length<!> }
|
||||
y.forEachRemaining { it -> it.<!UNSAFE_CALL!>length<!> }
|
||||
y.forEachRemaining { it -> it?.length }
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user