Useless call on not-null type

Reports calls on not-null receiver that make sense only for nullable receiver.

Several functions from the standard library such as orEmpty() or isNullOrEmpty have sense only when they are called on receivers of nullable types. Otherwise, they can be omitted or simplified as the result will be the same.

Remove redundant call and Change call to … quick-fixes can be used to amend the code automatically.

Examples:

fun test(s: String) {
    val x = s.orEmpty() // quick-fix simplifies to 's'
    val y = s.isNullOrEmpty() // quick-fix simplifies to 's.isEmpty()'
}

Inspection Details
Available in:	IntelliJ IDEA 2023.3, Qodana for JVM 2023.3
Plugin:	Kotlin, @snapshot@

Last modified: 13 July 2023