rust-random / rust-random/getrandom

Tracking issue for the next breaking release

Open
#800 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
580
Forks
259
No merged PRs in 30d

Description

Potential changes:

  • Migrate to extern_item_impls. See #796.
  • Remove free-standing functions in favor of SysRng. This would allow to simplify the implementation a bit, but would make rand_core a required dependency.
  • Use core::io::Error instead of the custom Error type?
  • Remove the file fallback from the default Linux backend.
  • Remove the wasm_js backend in favor of a separate extern_item_impls-based crate or moving getrandom support to wasm-bindgen/js-sys.
  • Use randomness API provided by std for targets with available std instead of re-implementing platform support in getrandom (see https://github.com/rust-lang/rust/issues/130703)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the checklist, issue #796, and the referenced Rust issue to understand which breaking-release changes are in scope. Examine the SysRng, rand_core, Linux fallback, wasm_js, and std-based API options mentioned here. Done means the selected migration and removals are agreed on and all applicable checklist items are implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
backend, operating-systems
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.