Seedable hashmap for testing?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This is inspired by the many regressions in https://github.com/rust-lang/rust/issues/128899 that appeared to be "sorting" issues but actually seem to be hashmap issues. It would be nice if we had some way, even if only for unstable/nightly/internal/literally-just-crater usage, to tweak std's hashmap (or just the RNG for it?) so that we could determine if the hashmap's iteration order is the reason a crate's tests are failing.
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 reading the regressions in rust-lang/rust#128899 and the surrounding discussion here. Investigate how std's hashmap iteration order and RNG are controlled, and consider the constraints of an unstable, nightly, internal, or crater-only mechanism; done means a concrete, testable way to vary hashmap behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100