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

This commit is contained in:

Ilmir Usmanov

2018-04-28 22:15:29 +03:00

parent 3f5a2c6427

commit f568149863

44 changed files with 2685 additions and 33 deletions

									
										compiler/testData/codegen/bytecodeText/inlineFromOtherModule.kt
									
Vendored

		+1
		
												View File
												
				@@ -1,3 +1,4 @@

				// KOTLIN_CONFIGURATION_FLAGS: ASSERTIONS_MODE=legacy

				fun foo() {

				    assert(1 == 1) { "Hahaha" }

				}