Preaching to the choir, as they say. I’m not sayin...
# kotlin-nativek
kpgalligan
06/04/2019, 1:45 PMPreaching to the choir, as they say. I’m not saying it shouldn’t raise priority, but there are many concurrent things happening and it likely won’t (much). I think a good first step is to see which other lang community takes ABI stability and creates direct interop. I’m assuming somebody in Rust-land will take a crack at it, but we’ll see. After that, we should keep in mind that direct Swift interop doesn’t mean these features will work. Generics will be more restrictive because you can’t cast around variance, and structs don’t exist in Kotlin (currently). I am currently (today) working on a POC to generate Swift code to improve the interface. Structs from (annotated) data classes, extension functions to translate them at the border. It may be a little too hacky for most, though, and will likely need to be an extension rather than an experimental feature like generics. Fundamentally, though, the lack of things like structs is impacting adoption with Swift-focused teams. I’ve talked to several and that is a common concern. How much and for how long is a different question. Most teams seriously looking at this now tend to be more aggressive in their tech, so may have much stronger opinions than others. Still, in general, structs would be nice.