As it stands any typedefs of that form which are not generic will be put into the header, this should cover most use cases but it's not impossible for people to do something like
pub type MyResult = Result<String, ()>;
which would put
typedef Result<String, ()> MyResult;
into the header file.
The two obvious ways to combat this are using #[repr(C)] (which rustc seems to be fine with) or adding a lint group and using #[allow(cheddar_typedef)] (I'm not sure whether this would actually work).
As it stands any typedefs of that form which are not generic will be put into the header, this should cover most use cases but it's not impossible for people to do something like
which would put
into the header file.
The two obvious ways to combat this are using
#[repr(C)](whichrustcseems to be fine with) or adding a lint group and using#[allow(cheddar_typedef)](I'm not sure whether this would actually work).