Mark Hammond
Mark Hammond
similar discussions for enums in #1470
The actual problem here is trying to use "transitive" external types. Eg, `crate1` defines `Type1`, `crate2` defines a `Dict1` dictionary which holds a `Type1`, then crate3 uses `Dict1` as an...
We'd probably take a fix for this, but the direction we are heading is to only support library mode, as that's the only way "external types" might work.
Yeah, that is what I meant - although part of (1) is already optional because UDL files are optional. (2) is necessary so we can "resolve" external types used by...
I assume the fix will be such that there's probably no real advantage/requirement to have tests in each of the bindings - indeed, it might even be such that a...
That seems correct for the current implementation, yeah. Isn't it getting easier to use library-mode?
Sorry I didn't look closer before and that I focused on library mode, but yeah, this a bug in uniffi - we shouldn't end up with dupe traitmethods. And I...
This is *almost* what's described at https://mozilla.github.io/uniffi-rs/proc_macro/index.html#types-from-dependent-crates, although I don't think this is supported for custom types. So I think the only path forward is to duplicate (or move) the...
Nope, the Ruby bindings rely entirely on external contributors.
Sorry for being so dense on a Monday morning, but what exactly would you like to see changed here? Or point to exactly what the "current type alias implementation" is?...