Skip to content

math/rand/v2: document PCG and ChaCha8 tradeoffs#79926

Open
harjothkhara wants to merge 1 commit into
golang:masterfrom
harjothkhara:gh-79891-rand-v2-source-guidance
Open

math/rand/v2: document PCG and ChaCha8 tradeoffs#79926
harjothkhara wants to merge 1 commit into
golang:masterfrom
harjothkhara:gh-79891-rand-v2-source-guidance

Conversation

@harjothkhara

@harjothkhara harjothkhara commented Jun 10, 2026

Copy link
Copy Markdown

Document that PCG is the fast general-purpose source and ChaCha8 trades
speed for stronger resistance to prediction.

Fixes #79891

Document that PCG is the fast general-purpose source and ChaCha8 trades speed for stronger resistance to prediction.

Fixes golang#79891
@google-cla

google-cla Bot commented Jun 10, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@harjothkhara harjothkhara marked this pull request as ready for review June 10, 2026 02:10
@gopherbot

Copy link
Copy Markdown
Contributor

This PR (HEAD: 45f06af) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/789040.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

math/rand/v2: include a bit of guidance on which source type to use

2 participants