rust-lang / rust-lang/rust-bindgen
Replacing native C types (Windows & Mac vs Linux)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
Bindgen nicely replaces occurrences of native C types with Rust types. For example:
#include <stdint.h>
typedef struct
{
const uint8_t b[16];
} MunGuid;
results in:
#[repr(C)]
#[derive(Clone, Copy)]
pub struct Guid {
pub b: [u8; 16usize],
}
It works. Lovely! One problem, once we run CI, it turns out that Ubuntu also generates this additional line
pub type __uint8_t = ::std::os::raw::c_uchar;
Even though bindgen is able to deduce that uint8_t is supposed to be u8, it still adds the __uint8_t type to the generated bindings.
One possible solution that I came up with to resolved this is to blacklist the __uint8_t type, but then bindgen stops automatically generating the #[derive(Clone, Copy)] attributes.
Is there a way to prevent the generation of "replaced" types?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the generated bindings from the issue's C example on Ubuntu and compare them with Windows or macOS output. Start by tracing how bindgen handles native typedefs and replacement types; done means preventing redundant replaced-type declarations without losing the generated derives.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100