Has anyone successfully used the latest prerelease version of Kotest (5.0.0.M4) with Kotlin/Native's...

# kotest

[charleskorn]

Has anyone successfully used the latest prerelease version of Kotest (5.0.0.M4) with Kotlin/Native's new memory model (using Kotlin 1.6.0-RC2)? With the new memory model enabled, none of my tests run.

I'm using the instructions in https://github.com/JetBrains/kotlin/blob/master/kotlin-native/NEW_MM.md to enable the new memory model.

[sam]

No work has been done on our side to test it / make it work

[sam]

when is this going final? 1.7 ?

[charleskorn]

Not sure - it will be available as a preview in 1.6.0 (https://youtrack.jetbrains.com/issue/KT-42296), and they’re currently working on getting it to an alpha state (https://youtrack.jetbrains.com/issue/KT-49520).

Could this change be the source of the issue?

Global properties are initialized lazily when the file they are defined in is first accessed. Previously global properties were initialized at the program startup. This is in line with Kotlin/JVM. As a workaround, properties that must be initialized at the program start can be marked with @EagerInitialization. Before using, consult the @EagerInitialization documentation.

(from https://github.com/JetBrains/kotlin/blob/master/kotlin-native/NEW_MM.md)

[sam]

Yeah possibly. I think with the new model being still quite early it won't make it into kotest 5.0 but maybe 5.1 or 5.2