Mark Hammond
Mark Hammond
Might actually be 1cb0ca0131fba6ec738b9861da46abf3a9d53a86 which broke it
Looks like it might be `impl_name` - https://github.com/mozilla/uniffi-rs/blob/a8da0375b66f5b433d79035976771d010151691b/uniffi_bindgen/src/bindings/python/templates/ObjectTemplate.py#L18-L22 - but that doesn't really make sense.
While @badboy has some great workarounds, I don't see any reason we wouldn't take a patch for a feature here. That might also dovetail into a future where people start...
I think we've removed it entirely!
The 2 challenges I see here are: * it's perfectly fine to export multiple impl blocks, including the impl of traits etc. Names can also be used across crates, wrapped...
> For example: > > #[derive(uniffi::Object(name="SomethingElse"))] > struct Something { > } > > #[uniffi::export] // no need to rename it here, if technically possible > impl Something { >...
See https://mozilla.github.io/uniffi-rs/latest/udl/callback_interfaces.html - callbacks are deprecated and can't be used here. You need to use `Arc`
damn - sorry about that, we shouldn't have made that change in a dot release.
Is there an actual use-case for this now? If not, it is starting look like experimenting with #2184 before landing this might make our future-selves less unhappy with our present-selves...
Thanks! But can we please get a test for this? Maybe specifying it for, eg, fixtures/ext-types/sub-lib?