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
@@ -1,7 +1,7 @@
|
||||
// FILE: KotlinFile.kt
|
||||
fun foo(javaClass: JavaClass) {
|
||||
javaClass.getSomething().<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
javaClass.something.<!INAPPLICABLE_CANDIDATE!>length<!>
|
||||
javaClass.getSomething().<!UNSAFE_CALL!>length<!>
|
||||
javaClass.something.<!UNSAFE_CALL!>length<!>
|
||||
}
|
||||
|
||||
// FILE: JavaClass.java
|
||||
|
||||
Reference in New Issue
Block a user