Missing getter-targeted annotations on annotation constructor parameters Support for this flag is going to be removed in the next major release. = 1.3: behavior changed, -Xnormalize-constructor-calls=disable can be used to temporarily revert to pre-1.3 behavior. Short summary: evaluation order with respect to class initialization is changed in 1.3 Incompatible changes Evaluation order of constructor arguments regarding call from Java) is out of the scope of this document.

Compatibility of Kotlin code from the other languages perspective (e.g. Remember that those definitions are given only for pure Kotlin. Source: source-incompatible change stops code that used to compile fine (without errors or warnings) from compiling anymoreīinary: two binary artifacts are said to be binary-compatible if interchanging them doesn't lead to loading or linkage errorsīehavioral: a change is said to be behavioral-incompatible if one and the same program demonstrates different behavior before and after applying the change

In this document we introduce several kinds of compatibility:

While most of the language changes were already announced through other channels, like update changelogs or compiler warnings, this document summarizes them all, providing a complete reference for migration from Kotlin 1.2 to Kotlin 1.3. The former says that constructs which obstruct language evolution should be removed, and the latter says that this removal should be well-communicated beforehand to make code migration as smooth as possible. Keeping the Language Modern and Comfortable Updates are among the fundamental principles in Kotlin Language Design.

Kotlin loop range