Ilmir Usmanov
f568149863
Previously, assert was just a regular function and its argument used to be computed on each call (even if assertions are disabled on JVM). This change adds support for 3 new behaviours of assert: * always-enable (independently from -ea on JVM) * always-disable (independently from -ea JVM) * runtime/jvm (compile the calls like javac generates assert-operator) * legacy (leave current eager semantics) - this already existed Default behaviour is legacy for now. The behavior is changed based on -Xassertions flag. #KT-7540: Fixed
38 lines
730 B
Kotlin
Vendored
38 lines
730 B
Kotlin
Vendored
// IGNORE_BACKEND: JS
|
|
// KOTLIN_CONFIGURATION_FLAGS: ASSERTIONS_MODE=jvm
|
|
// WITH_RUNTIME
|
|
// WITH_COROUTINES
|
|
// COMMON_COROUTINES_TEST
|
|
|
|
import helpers.*
|
|
import COROUTINES_PACKAGE.*
|
|
|
|
class Checker {
|
|
suspend fun check() {
|
|
assert(false)
|
|
}
|
|
}
|
|
|
|
class Dummy
|
|
|
|
fun enableAssertions(): Checker {
|
|
val loader = Dummy::class.java.classLoader
|
|
loader.setDefaultAssertionStatus(true)
|
|
val c = loader.loadClass("Checker")
|
|
return c.newInstance() as Checker
|
|
}
|
|
|
|
fun builder(c: suspend () -> Unit) {
|
|
c.startCoroutine(EmptyContinuation)
|
|
}
|
|
|
|
fun box(): String {
|
|
var c = enableAssertions()
|
|
try {
|
|
builder { c.check() }
|
|
return "FAIL 6"
|
|
} catch (ignore: AssertionError) {
|
|
}
|
|
|
|
return "OK"
|
|
} |