Ilmir Usmanov
df4dcc0f8e
if assertions mode is not LEGACY. This is done since assertions can be disabled (in both compile time and runtime) and thus, the data flow info is not reliable anymore. #KT-24529: Fixed
38 lines
549 B
Kotlin
Vendored
38 lines
549 B
Kotlin
Vendored
// !IGNORE_DATA_FLOW_IN_ASSERT
|
|
// SKIP_TXT
|
|
// WITH_RUNTIME
|
|
|
|
fun test1(s: String?) {
|
|
assert(s!!.isEmpty())
|
|
s?.length
|
|
}
|
|
|
|
fun test2(s: String?) {
|
|
assert(s!!.isEmpty())
|
|
s!!.length
|
|
}
|
|
|
|
fun test3(s: String?) {
|
|
assert(s!!.isEmpty())
|
|
s<!UNSAFE_CALL!>.<!>length
|
|
}
|
|
|
|
fun test4() {
|
|
val s: String? = null;
|
|
assert(s!!.isEmpty())
|
|
s?.length
|
|
}
|
|
|
|
fun test5() {
|
|
val s: String? = null;
|
|
assert(s!!.isEmpty())
|
|
s!!.length
|
|
}
|
|
|
|
fun test6() {
|
|
val s: String? = null;
|
|
assert(s!!.isEmpty())
|
|
s<!UNSAFE_CALL!>.<!>length
|
|
}
|
|
|