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
Currently our ExternType trait has the C++ type_id as an associated type, which means a single Rust type can have at most one ExternType impl and therefore at most one type_id associated to them.
This makes it possible to work with types that might be exposed at multiple different locations on the C++ side.
unsafeimplExternTypefori16{typeId = cxx::type_id!("std::int16_t");}unsafeimplExternTypefori32{typeId = cxx::type_id!("std::int32_t");}// this works regardless of whether pid_t is typedef'd to// i16 or i32 on the platformunsafeimplExternTypeAlias<cxx::type_id!("pid_t")>for libc::pid_t{}
The text was updated successfully, but these errors were encountered:
Currently our ExternType trait has the C++ type_id as an associated type, which means a single Rust type can have at most one ExternType impl and therefore at most one type_id associated to them.
We should consider adding something like:
and then substituting the following change to how we do type_id verification:
This makes it possible to work with types that might be exposed at multiple different locations on the C++ side.
The text was updated successfully, but these errors were encountered: