@channel Kotlin/Native team is pleased to announce release v0.7.1 of our toolchain. This is a bugfixing release, including the following features: * Bugfixes in the runtime (indexOf, GC for kotlin.Array, enum equality) and the compiler * Fix NSBlock problem, preventing upload of binaries to the AppStore * Create primitive type boxes and kotlin.String as frozen by default * Support Gradle 4.7, provide separate run task for each executable * Support XCode 9.4 and CoreML and ClassKit frameworks on Apple platforms * Improved runtime Kotlin variable examination * Minor performance optimizations in compiled code and runtime * Add

disableDesignatedInitializerChecks

definition file support Binaries: * https://download.jetbrains.com/kotlin/native/builds/releases/0.7.1/macos/kotlin-native-macos-0.7.1.tar.gz * https://download.jetbrains.com/kotlin/native/builds/releases/0.7.1/linux/kotlin-native-linux-0.7.1.tar.gz * https://download.jetbrains.com/kotlin/native/builds/releases/0.7.1/windows/kotlin-native-windows-0.7.1.zip GitHub release page is https://github.com/JetBrains/kotlin-native/releases/tag/v0.7.1

In the notes GC is mentioned for kotlin.Array. What is GC (don't think it stands for Garbage Collection)?

yes, GC is for Garbage collection, and in https://github.com/JetBrains/kotlin-native/commit/2934588bbed99b7dbb4c8949c6d580da3d9cdf49 we fixed issue with cyclic collector involving kotlin.Array

So a GC system is currently being developed for Kotlin Native?

GC is a short term for automated memory management, and Kotlin does have it from the day one. Cycle collector was unable to collect cycles with arrays, due to an optimization, which was ignoring leaf objects in cyclic garbage analysis

In other words the GC handles a small part of Kotlin Native that can't be handled by ARC.

Not exactly, GC and automated memory management are same concept, and could be used interchangeable