Tianyu Geng
e1b542314a
There is some behavior change regarding the new WrapWithSafeLetCall quickfix
1. it now works correctly on binary expressions by wrapping it with `()`
2. it now looks for a nullable position upward and do the modification there,
if possible. For example, consider the following code
```
fun bar(s: String): String = s
fun test(s: String?) {
bar(bar(bar(<caret>s)))
}
```
After applying this fix, FE1.0 yields
```
bar(bar(s?.let { bar(it) }))
```
while the new implementation yields
```
s?.let { bar(bar(bar(it))) }
```
This behavior aligns with FE1.0 if `bar` accepts nullable values.
16 lines
446 B
Kotlin
Vendored
16 lines
446 B
Kotlin
Vendored
// "Wrap with '?.let { ... }' call" "false"
|
|
// ACTION: Add non-null asserted (!!) call
|
|
// ACTION: Convert to run
|
|
// ACTION: Convert to with
|
|
// ACTION: Replace with safe (?.) call
|
|
// ACTION: Surround with null check
|
|
// ERROR: Only safe (?.) or non-null asserted (!!.) calls are allowed on a nullable receiver of type B?
|
|
// WITH_RUNTIME
|
|
|
|
class A {
|
|
fun foo() {}
|
|
}
|
|
class B(val a: A)
|
|
fun test(b: B?) {
|
|
b<caret>.a.foo() // b.a is UNSAFE_CALL
|
|
} |