<https://github.com/swiftlang/swift-java>
Will th...
# swift-exports
Sanjeeviraj M
09/26/2024, 1:09 PMhttps://github.com/swiftlang/swift-java
Will this make kotlin interop easier?
đź‘€ 2
f
François
09/26/2024, 1:17 PMI didn’t know this one
François
09/26/2024, 1:18 PMthis project is at early stage, so wait and see...
j
jw
09/26/2024, 1:47 PMNo. This is for the JVM.
đź‘Ť 2
r
russhwolf
09/27/2024, 2:42 AMIt's the opposite. It would presumably be helpful if you want to write Swift for Android instead of Kotlin for iOS.
j
jw
09/27/2024, 2:43 AMWell, not Android, because Swift to Java depends on Project Panama's new FFI so you're JDK 22+ only.
jw
09/27/2024, 2:47 AMThat being said, someone could write a JNI-based solution here as well. You'd have to use SwiftSyntax to parse the swift and find all the annotated points and then generate all the yucky JNI code as well as honor whatever calling convention they've defined. I would assume the annotations are a shortcut to the regular C calling convention since they build on top of jextract rather than use their own tool.
jw
09/27/2024, 2:48 AMBut then you've always been able to expose a C ABI from Swift and call it via JNI. That's nothing new. The only new thing here is the automated tooling and that automated tooling is JDK 22+ only.
đź‘Ť 3
r
russhwolf
09/27/2024, 2:49 AMyeah that's fair. I know of at least one team that's been running Swift on Android since 2018. I was assuming the new tooling would make that easier but didn't realize the JDK 22 requirement
đź‘Ť 1
j
Jeffrey Macko
12/11/2024, 9:08 PMWhat is the state of swift/ios interop today ?
In recent weeks, the swift-java project has seen growth.
I wonder if anyone has revisited its interoperability potential, especially with Kotlin, given the following updates:
• The extract tool might eventually support generating legacy-compatible sources that wouldn’t require JEP-454, instead leveraging existing JNI facilities. However, the current focus remains on modern foreign function and memory APIs.
• There’s ongoing work to make it Android-compatible (PR #144), and the repository seems to incorporate Kotlin dependencies.
• Swift binaries themselves are now building and running on Android (documentation).
• People use this project to create stuff like FlutterSwift
I know much of this may seem like conjecture or anecdotal evidence, but do you think this points to a trend toward making Swift more interoperable with Kotlin in the future?
44 Views