Mark Hammond

> Which means that it is impossible to call `foo` with a value returned from `makeStruct`, from Kotlin's side, it seems obvious that `foo` should instead be > > >...

Callback interfaces can have async methods - https://mozilla.github.io/uniffi-rs/latest/futures.html#exporting-async-trait-methods - which I think is roughly what you are asking for?

You should find your generated code includes code generated by https://github.com/mozilla/uniffi-rs/blob/2d1912a57f731f9fc4936d0cc5270c3f416a1044/uniffi_bindgen/src/bindings/swift/templates/wrapper.swift#L17-L19 - we *think* it is this block which does the import you need. What is the name of the...

Thanks - I'll try and better understand this later. > It does include that, but it's not enough (at least not in my case) Is the code generated there actually...

We don't support result types anywhere other than results. We'd like to, but it's quite a bit more difficult than you'd think.

I think the entire renaming mechanism is now unused since Python started using a pipeline.

That sounds quite exciting! > Separate library from the Rust crate > * Fairly clean, but it's one more file for the user to copy around (`libfoo.so`, `libfoo_jni.so`, `Foo.kt`) That...

It really does look like you must be using the `--xcframework` param.

I don't fully understand your environment - uniffi supports multiple crates fine, but does not support multiple *libs* - ie, you need to build these crates into a single .a...

My question is how these crates are built - how many *libraries* do your 2 crates make? We certainly support many crates compiled into 1 library, but do not support...