rust-lang / rust-lang/rust-bindgen
Use MaybeUninit<> for generated padding where available.
Open
Nobody has claimed this yet.
enhancement
help wanted
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
When the rust-target supports MaybeUninit<>, we should technically use that when we inject padding into a struct.
This should be straight-forward and I'm happy to mentor this. See https://github.com/rust-lang/libc/issues/1453.
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
The issue names no file or test. Start by reading the linked rust-lang/libc issue and locating the generated-padding path for Rust targets that support MaybeUninit<>. Done means generated padding uses MaybeUninit<> where available while preserving behavior on unsupported targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100