rust-random / rust-random/rand
Tracker: breaking API changes
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 2.1k
- Forks
- 512
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 7
Description
Pub fn ThreadRng::reseed returns a Result<(), SysError>. I do not think this is useful in practice; we already handle the same error internally on initialization and periodic reseeding by panicking.
- Action: remove return value of fn
ThreadRng::reseed
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
Locate the public ThreadRng::reseed entry point and inspect its callers, including the initialization and periodic reseeding paths mentioned in the issue. Remove the return value and verify that the existing error-handling behavior remains intact wherever the method is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100