bendk

Yes that seems right to me. Let's close.

I'm +1 on this. I've wanted support for `..` patterns and calling methods for a while now.

Completely unrelated to this patch, but I believe your build issue is caused by mixing UniFFI versions. That [error message](https://github.com/mozilla/uniffi-rs/blob/760660b3f1d70e54363836bf371a85fa5d7913d4/uniffi_meta/src/reader.rs#L262) was in 0.26.x and 0.27.x, but removed in [0.28.x](https://github.com/mozilla/uniffi-rs/blob/2296746b335ff27f49a669a49e4fbbfca9ef9214/uniffi_meta/src/reader.rs#L262). My...

This feels similar in spirit to my PR to add the `ffi-trace` feature https://github.com/mozilla/uniffi-rs/pull/2211. What do others think about putting these logging statements behind that feature flag? In general, my...

I think #2275 covers this one and I'm going to close. Please re-open if you have use-cases that it doesn't meet.

This would be great and something that we've discussed. IMO the best way would be to do this in the `uniffi.toml` file, since you may want to rename things differently...

Can someone explain their use case a bit better? My first question is why not rename the struct in Rust to match what you want in the foreign language?

Thanks for the example, that makes a lot of sense. It seems like this is very similar to the `uniffi.toml` method, but for your use-case it's better to specify the...

I haven't had time to work on this issue, but I'm currently starting some work that I think will make it much easier to implement these kinds of features and...

I feel very on the fence about this one, but I think I'm leaning towards "it's okay". Like Mark says, it seems fine to say that passing things across the...