rust-fuzz / rust-fuzz/arbitrary
Avoid returning errors where possible
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 880
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/rust-fuzz/arbitrary/commit/1d2f65360f634968b5525f4d6430a88a376277f0
Next breaking release that we make, I think we can remove the fallibility from
theArbitrarytrait and all theUnstructuredmethods.
This wasn't addressed in the discussion about 1.0 https://github.com/rust-fuzz/arbitrary/issues/62 .
Is this still something we want to do? Are you open for a PR implementing it?
Contributor guide
No contributing guide indexed for this repository
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 commit 1d2f65360f634968b5525f4d6430a88a376277f0 and the discussion in issue 62. Confirm whether removing fallibility from the Arbitrary trait and all Unstructured methods is still wanted; done requires an agreed direction before implementation, since no specific files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100