azalea/kotlin-fork
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

FIR checker: differentiate UNSAFE_CALL from INAPPLICABLE_CANDIDATE

Browse Source 
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:
Jinseong Jeon
2021-01-26 16:03:27 -08:00
committed by Mikhail Glukhikh
parent 4b823eca21
commit e72ddbcbfe
275 changed files with 1426 additions and 1388 deletions
Download Patch File Download Diff File Expand all files Collapse all files
compiler/testData/diagnostics/tests/smartCasts/exclUnderAnd.fir.kt
Vendored
+4 -4
View File
@@ -2,12 +2,12 @@ class D(val a: String, val b: Boolean)
fun foo(p: Boolean, v: D?): String {
if (p && v!!.b) v.a
else v.<!INAPPLICABLE_CANDIDATE!>a<!>
else v.<!UNSAFE_CALL!>a<!>
if (p && v!! == D("?", false)) v.a
else v.<!INAPPLICABLE_CANDIDATE!>a<!>
if (p || v!!.b) v.<!INAPPLICABLE_CANDIDATE!>a<!>
else v.<!UNSAFE_CALL!>a<!>
if (p || v!!.b) v.<!UNSAFE_CALL!>a<!>
else v.a
if (p || v!! == D("?", false)) v.<!INAPPLICABLE_CANDIDATE!>a<!>
if (p || v!! == D("?", false)) v.<!UNSAFE_CALL!>a<!>
else v.a
return ""
}