You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To specify the bridge type for custom types. This is no longer needed now that New custom type system #2150 is merged.
To know the FFI type when lowering. However, this can be determined using the proc-macro metadata and we're already translating all UDL definitions to proc-macro invocations.
To fill in required fields for the uniffi_meta types. We can avoid this by making uniffi_udl generate its own types, rather than the uniffi_meta types. We don't need to all of that data, we just need to enough to generate the proc-macro calls. One side benefit of this is that we could remove fields in uniffi_meta that only exist to support uniffi_udl (example)
The only downside I can see is that maybe the error messages will get worse if you misspell a type. I'm not too worried about this since I'm more and more convinced we should be pushing users away from UDL anyways.
The text was updated successfully, but these errors were encountered:
We currently need these for a few reasons and I'm hoping to make them all obsolete.
UniffiTag
system to use. This won't be necessary after MakeUniffiTag
consistent for UDL and procmacros #1865.uniffi_meta
types. We can avoid this by makinguniffi_udl
generate its own types, rather than theuniffi_meta
types. We don't need to all of that data, we just need to enough to generate the proc-macro calls. One side benefit of this is that we could remove fields inuniffi_meta
that only exist to supportuniffi_udl
(example)The only downside I can see is that maybe the error messages will get worse if you misspell a type. I'm not too worried about this since I'm more and more convinced we should be pushing users away from UDL anyways.
The text was updated successfully, but these errors were encountered: