rust-lang / rust-lang/rust-bindgen
quickchecking with whitelisting and opaque types
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.3k
- Forks
- 829
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 15
Description
The quickchecking crate, for property testing with fuzzed C headers doesn't exercise whitelisting or opaque types.
If those features were excercised, the tests might verify that if whitelisting is employed,
those types appear in the bindings and that anything flagged opaque isn't translated beyond "a blob of bytes".
Corresponds to extending #970
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
Start by inspecting the quickchecking crate and the work described in issue #970. Extend the property tests to exercise whitelisting and opaque types; done means the tests verify whitelisted types appear in bindings and opaque types remain only a blob of bytes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, rust
- Domain
- compilers, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100