swift-java

Another approach is swift-java, which uses Swift macros and also supports Panama. https://github.com/swiftlang/swift-java

It's worth pointing out that the example you linked with the cdecl is not showcasing the swift-java interoperability but using "raw" JNI patterns as if you would do it with C. This example does showcase the interoperability: https://github.com/swiftlang/swift-android-examples/tree/mai... you don't have to annotate or write any "weird" cdecls or really touch JNI details yourself when using the swift-java interop support https://github.com/swiftlang/swift-java

> Let's say i want to expose an async call to a local sqlite instance on android. I don’t know, I don’t do android dev. I just made sure my library was running on it then moved on. I know Swift is working on having bidirectional interoperability with Java[1], so I guess when they do it’ll just work? But I did not dig more on the subject. Regarding the size I’m not sure as I never compiled a binary that is actually useful. I make sure everything runs, but as I’m building a library this goes to building the tests then running them on WASI and that’s it. Regarding the Swift toolchain version, using swiftly[2] is recommended nowadays if you don’t need Xcode. Using the default toolchain provided by Xcode usually brings trouble when using SDKs. Using swiftly you’ll get the same experience as on Linux basically. (This will probably change, but i

Tangential: Apple has a new Swift Java bridge which is pretty cool, supporting both JNI and Panama. I’ve been porting it to Android this past week. https://github.com/swiftlang/swift-java

> It makes me wonder how they are dealing with memory management when Java objects are being used from Swift It uses Swift macros to add a `JavaObjectHolder` property to Swift types annotated with `@JavaClass`[0]. `JavaObjectHolder` is a Swift class that takes a global JNI reference to the Java object, and releases it when the holder is destroyed[1]. The result is that a codegen utility emits Swift structs[2] that wrap the JNI values, and the JNI glue code for method invocation is applied at compile-time when the macros are expanded. [0] https://github.com/swiftlang/swift-java/blob/e7d7a217e37d49b... [1] https://github.com/swiftlang/swift-java/blob/main/Sources/Ja... [2] https://github.com/swiftlang/swift-java/blob/main/Sources/Ja...

This sounds useful. Here are links that actually load on my phone. - https://github.com/swiftlang/swift-java - https://forums.swift.org/t/improving-swift-support-and-inter...