rust-random / rust-random/getrandom
Support for non-blocking getrandom
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 580
- Forks
- 259
- PR merge metrics
- No merged PRs in 30d
Description
In some scenarios (e.g. for seeding HashMap) it's desirable to get potentially less secure numbers than to block indefinitely. The motivation is largely equivalent to motivation behind the GRND_NONBLOCK flag used in the getrandom syscall. We probably should add support for such scenarios, either by adding an additional argument or by introducing a separate set of non-blocking functions.
Relevant PRs: #353 #352
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 reading the getrandom syscall documentation and the relevant prior discussions in PRs #353 and #352. Compare the proposed API approaches for non-blocking randomness, then establish cross-platform behavior and tests; done means callers can request non-blocking randomness with documented semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100