Create testing corpus of rust constructs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.4k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
The project doesn't currently support all rust constructs. It's not clear what is supported and what is not, so users will suddenly trip over issues.
One idea to generate such a list is to try to compile (not run) all no_std and no alloc crates on crates.io and see which fail...similar to what miri does.
Another way would be to create a rust program generator and "fuzz".
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 reviewing the project's current Rust construct support and how unsupported constructs are detected. Compare the proposed approaches: compiling no_std and no_alloc crates from crates.io, or generating and fuzzing Rust programs. Done should include a defined corpus or generator and a documented view of which constructs are supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100