Files
kotlin-fork/compiler/testData/codegen/box/assert/jvm/interfaceAssertionsDisabled.kt
T
Ilmir Usmanov f568149863 Implement new assert semantics in back-end
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
2018-05-21 20:43:37 +03:00

55 lines
1.2 KiB
Kotlin
Vendored

// IGNORE_BACKEND: JS
// KOTLIN_CONFIGURATION_FLAGS: ASSERTIONS_MODE=jvm
// WITH_RUNTIME
interface Checker {
fun checkTrue(): Boolean {
var hit = false
val l = { hit = true; true }
assert(l())
return hit
}
fun checkFalse(): Boolean {
var hit = false
val l = { hit = true; false }
assert(l())
return hit
}
fun checkTrueWithMessage(): Boolean {
var hit = false
val l = { hit = true; true }
assert(l()) { "BOOYA" }
return hit
}
fun checkFalseWithMessage(): Boolean {
var hit = false
val l = { hit = true; false }
assert(l()) { "BOOYA" }
return hit
}
}
class ShouldBeDisabled : Checker {}
class Dummy
fun disableAssertions(): Checker {
val loader = Dummy::class.java.classLoader
loader.setDefaultAssertionStatus(false)
val c = loader.loadClass("ShouldBeDisabled")
return c.newInstance() as Checker
}
fun box(): String {
var c = disableAssertions()
if (c.checkTrue()) return "FAIL 0"
if (c.checkTrueWithMessage()) return "FAIL 1"
if (c.checkFalse()) return "FAIL 2"
if (c.checkFalseWithMessage()) return "FAIL 3"
return "OK"
}