Mark Hammond
Mark Hammond
> Each crate is a library but since there are dependencies between them, building mylib with `cargo swift` also builds mylib-types and puts them under the same framework producing single...
I'm not really sure what you mean exactly, but maybe you are describing #2592?
> Arc::clone seems to produce a new pointer each time. The pointer value will be different, but it should point to the same object - that's the entire point of...
The kotlin side isn't aware these wrap the same objects - for a normal interface you could expose `Eq` and `Hash` as described [here](https://mozilla.github.io/uniffi-rs/latest/types/interfaces.html#exposing-methods-from-standard-rust-traits) - I *think* that should be...
(actually, traits with foreign are unlikely to work in that scenario - that would require the kotlin code implementing the trait to also know how to implement `Eq` and `Hash`,...
Yeah, I should have been clearer - I'm not surprised it doesn't work for normal traits, but I think I can see how it could. For "foreign traits" I'm struggling...
It might be possible, but it's not clear that would be a good thing to implement by default - it's closer to the concept of "identity" rather than "equality". It...
I think the issue here is that there's no way for traits to define `Eq` etc?
> > I think the issue here is that there's no way for traits to define `Eq` etc? > > I think this seems like a language constraint. I don’t...
It sounds like this is the same as #2402?