Another question, is Kotlin Native impacted in any...

# kotlin-native

[galex]

Another question, is Kotlin Native impacted in any way by Swift version changes? iOS devs tell me it could be unsuitable for an iOS project because Swift changes a lot in every version, and they don’t want to be dependent on kotlin native to have to update its libraries we would build. WDYT?

[russhwolf]

Kotlin/Native interfaces with Objective-C, not directly with Swift. This means that it can't access Swift things that aren't visible to Objective-C, but it also means that Swift instability shouldn't be a problem.

[russhwolf]

I think that might change once Swift becomes ABI-stable, but you'd have to ask Jetbrains for an actual roadmap there (and I suspect they're not quite ready to give one)

[Sam]

Swift/iOS dev here and I concur with Russell. The main part that a swift dev may object to is that certain Kotlin constructs can produce awkward interfaces that Swift devs may find distasteful. I’m speaking mostly of companion objects and having to return KotlinUnit from void functions. I wrote some code over the weekend that throws an IllegalStateException and looking at the generated signature it might also be awkward. I need to explore that more.

[galex]

Thank you both @russhwolf @Sam!