A modern programming language that makes developers happier.

kotlinlang

I noticed the latest *1.9.0-Beta-104* includes <https://github.com/JetBrains/kotlin/commit/f4e8ae51910a64bc152905e2dbaeaaaff7aeb895|this commit>, which adds `@ExperimentalForeignApi` to Kotlin/Native <https://kotlinlang.org/api/latest/jvm/stdlib/kotlinx.cinterop/|kotlinx.cinterop> APIs, like `CPointer`, `memScoped`, `alloc`, `convert`, as well as most C/ObjC interop generated APIs. Could someone please explain this change? Are apps that use C interop expected to opt in to this annotation globally?

The linked issue seems to cover it pretty well <https://youtrack.jetbrains.com/issue/KT-57728>

Thanks, I was just beginning to read the issue. Probably should have done that before asking as it does explain things more.

So after reading the issue, it doesn't explicitly answer my question, but my assumption would be a project that requires these C/ObjC interop APIs does need to opt in to this `@ExperimentalForeignApi` annotation (as well as possibly the `@BetaInteropApi` warning), and does so with the knowledge that these APIs may change in the future, replaced by better designed and documented alternatives. I'm also assuming any such changes would come after KMM's stability announcement and Kotlin 2.0.

That's about my read. You already are subject to these semantics, it's just that they weren't communicated anywhere. The opt-in annotation forces that to be acknowledged, even if you suppress it globally.

That makes sense. The documentation has definitely been lacking for these APIs, at least in the KDocs. But the <https://kotlinlang.org/docs/native-c-interop.html|documentation> that does exist never explicitly mentions API stability, which I'm sure will be updated with this info for the 1.9 release. Good to know this will eventually improve, even if it does mean migrating some code in the future.