bendk
bendk
I like this direction. Couple thoughts: - Maybe it should even be `InternalError` or `PanicError`, since you can't recover from them in general. - I think there are a couple...
My general feeling about this is that there should be some sort of conversion step for the `ComponentInterface` when generating the bindings code. The `ComponentInterface` that we generate from the...
I think I actually confused myself. The issue you bring up is very real, but I think there's a solution to it. I just updated the proposal to reflect that....
After thinking about this some more, I think there's a better way to handle this: - Keep the `FfiConverter` trait the same - Require proc-macro users to call a global...
Go for it. I think you're idea is a good starting point and I'm still not convinced that my proposal is worth the added complexity.
Maybe I should clarify what I mean by "Go for it". - I'm pretty sure we currently implement `FFIConverter` on the type itself for all types UniFFI supports. If not,...
I don't know how to do this in general, since which functions need `override` is language-specific. However, a `to_string` method is very common and it could be nice to support....
Let's wait for work Tarik is doing to move bindings to their own crate before we touch this one.
I think this can be fixed by using the `uniffi_testing` library, but that's currently only used by `uniffi-bindgen-gecko-js`.
This is the current system, but it's not really great. It would be wonderful to have some sort of integration that does this manually. Maybe gradle could help?