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/comparisonUnderAnd.fir.kt
Vendored
+12 -12
View File
@@ -6,30 +6,30 @@ fun foo(x : String?, y : String?) {
y.length
}
else {
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
if (y != null || x == y) {
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
else {
// y == null but x != y
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
if (y == null && x != y) {
// y == null but x != y
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
else {
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
if (y == null || x != y) {
x.<!INAPPLICABLE_CANDIDATE!>length<!>
y.<!INAPPLICABLE_CANDIDATE!>length<!>
x.<!UNSAFE_CALL!>length<!>
y.<!UNSAFE_CALL!>length<!>
}
else {
// Both not null