rust-fuzz / rust-fuzz/arbitrary
List of breaking changes for next breaking release
Open
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/pull/216
- remove split between
try_size_hintandsize_hint - bump MSRV to latest stable
- https://github.com/rust-fuzz/arbitrary/issues/201
- flip
size_hint's parameter from current depth to max-depth - add support for
a..branges inUnstructured::int_in_range
- not breaking, but could be nice: https://github.com/rust-fuzz/arbitrary/issues/191
- stop returning an error from many
Unstructuredmethods that are actually infallible now (and maybe also introducetry_*variants that return aResultand don't create dummy values when the underlying data is exhausted)
Anything else?
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 linked pull request 216, issues 201 and 191, and the two issue comments describing the size_hint parameter change and range support. Resolve which breaking changes belong in the next release, define the final scope and acceptance criteria, and track each selected item to completion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100