From c2f03b4d288052408314c2b18f4c27d482e95b6a Mon Sep 17 00:00:00 2001 From: Svyatoslav Scherbina Date: Tue, 11 Jan 2022 12:21:55 +0000 Subject: [PATCH] Deprecate freezing in kotlin-native/NEW_MM.md --- kotlin-native/NEW_MM.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kotlin-native/NEW_MM.md b/kotlin-native/NEW_MM.md index 73e248b13a1..be0289c0862 100644 --- a/kotlin-native/NEW_MM.md +++ b/kotlin-native/NEW_MM.md @@ -26,6 +26,8 @@ The new MM also brings another set of changes: As a workaround, properties that must be initialized at the program start can be marked with `@EagerInitialization`. Before using, consult the [`@EagerInitialization`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.native/-eager-initialization/) documentation. * `by lazy {}` properties support thread-safety modes and do not handle unbounded recursion. This is in line with Kotlin/JVM. * Exceptions that escape `operation` in `Worker.executeAfter` are processed like in other parts of the runtime: by trying to execute a user-defined unhandled exception hook or terminating the program if the hook was not found or failed with an exception itself. +* In the new MM, freezing is deprecated and will be removed in one of the future releases. + Don't use freezing if you don't need your code to work with the old MM. ## Enable the new MM