Alexander Cyon

@mhammond Yes @micbakos-rdx phrased it badly, i think: > Consider changing how Vec is translated in Kotlin. However, this solution is only valid for our use case. So we are...

And what @micbakos-rdx wrote above: > 2. Explore the possibility of instructing UniFFI to override the equals method of the generated data class, allowing it to follow the equality check...

> Another possibility would be to have a simple boolean in this file, meaning this entire crate simply opts out of having a bytes type for types inside it. Yes,...

Thx! I will give it a go

Yes it is manifold: 1) there is a bug, where I'm allowed to attach `#[uniffi::constructor]` to a Record without compilation error, but it is not exposed. 2) Yes I would...

@mhammond alongside of default constructor - which I also would like to be able to make private instead of public as mentioned in another Matrix thread

Yes to be able to skip generating the memberwise init, I went into implementation details... that since we already code for generating the memberwise init and we could simply toggle...

@mhammond I was gonna ask, what is the status of support for methods on Records? "Status" meaning two things I guess: 1. How hard/complex would it be to add support...

@mhammond When considered, I think it makes sense to split the "add support for #[uniffi::export] for methods on Records"-feature request into two: 1. support for non-mutating methods (`fn get_foo_with_logic(&self) ->...

@mhammond As a UniFFI author and consumer, frankly, I don't care about it being inefficient 😄 that "cost" is far far a smaller cost then as an author having to...