Any plan for swift interop support instead of obje...

# kotlin-native

[brabo-hi]

Any plan for swift interop support instead of objective C?

[russhwolf]

https://youtrack.jetbrains.com/issue/KT-49521

[brabo-hi]

@russhwolf thanks for sharing that

[Jon Bailey]

A vague sense of hope can be found in the “KMP is now stable” blogpost from the other day, where it’s mentioned as a future update: https://blog.jetbrains.com/kotlin/2023/11/kotlin-multiplatform-stable/#explore-the-future-of-kotlin-multiplatform

[Edoardo Luppi]

I think the Kotlin team is busy with K2. Once K2 is delivered, other major enhancements will be unlocked

[Landry Norris]

Swift also just recently stabilized the ABI enough for interop to work. Hence why C++ is the only language (right now) with pure-Swift interop (some claim Swift interop, but if you look closely, they require objc annotation), and even the C++ version is experimental.

[Jon Bailey]

Swift’s stable ABI was in 2019/iOS 12.2 which seems quite a while ago? Though I don’t know too much how interoperability would work so maybe that’s recent to the amount of work required.

[Landry Norris]

Looking at their docs again, it looks like I meant the section labeled 'Module stability (and ABI stability)', not ABI stability. Swift 5 brought ABI stability that allowed to switch standard libraries. Stability across Swift compilers (what you'd want to have to enable interop) is still in progress.
https://www.swift.org/blog/abi-stability-and-more/

[Landry Norris]

I'd argue what they have is just part of ABI stability, since compiler and library stability are still in progress, but I guess those are the terms they use.

[Edoardo Luppi]

Just seen this.

[Edoardo Luppi]

Should answer your question.

[Edoardo Luppi]

Ah well, it was already written in the blog post lol, had forgotten about it

[brabo-hi]

@Edoardo Luppi thanks for sharing