crypto/rand: make Read not escape the byte slice

[mateusz834]

          │ /tmp/before │             /tmp/after             │
          │   sec/op    │   sec/op     vs base               │

ReadAllocs-12 3.050µ ± 0% 2.912µ ± 0% -4.52% (p=0.000 n=10)

          │ /tmp/before  │             /tmp/after              │
          │     B/s      │     B/s       vs base               │

ReadAllocs-12 320.2Mi ± 0% 335.3Mi ± 0% +4.73% (p=0.000 n=10)

          │ /tmp/before  │              /tmp/after               │
          │     B/op     │     B/op      vs base                 │

ReadAllocs-12 1.000Ki ± 0% 0.000Ki ± 0% -100.00% (p=0.000 n=10)

          │ /tmp/before │             /tmp/after              │
          │  allocs/op  │ allocs/op   vs base                 │

ReadAllocs-12 1.000 ± 0% 0.000 ± 0% -100.00% (p=0.000 n=10)

[gopherbot]

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

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

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.

[gopherbot]

Message from Gopher Robot:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 1: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 0654f22) has been imported to Gerrit for code review.

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

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.

[gopherbot]

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-12T19:04:09Z","revision":"af8e49a2bd486cd303a3c8847c5bbf1c04115086"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 1:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 2: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-12T19:10:40Z","revision":"f70f54162b68f90ffa0eb5800d0ad6cae47f2da7"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

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

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

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.

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 2: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-arm64 has failed with summary (view all results):

---

FAILURE

• go on master (change 578516)

Tests failed. See all test results.

Error: shard 1: failed to run "go tool dist test -json": exit status 1

Links:

• shard 1 build page
• shard 1 test results
• shard 1 "go tool dist test -json" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 2: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 3: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-13T05:48:21Z","revision":"98c3ed463e44bd7a0424fce0c7c88571a281bdfa"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 3: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-arm64 has failed with summary (view all results):

---

FAILURE

• go on master (change 578516)

Tests failed. See all test results.

Error: shard 1: failed to run "go tool dist test -json": exit status 1

Links:

• shard 1 build page
• shard 1 test results
• shard 1 "go tool dist test -json" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 3: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 81fe51c) has been imported to Gerrit for code review.

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

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.

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 4: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-13T06:28:15Z","revision":"90bf2555ac1ed46fb151d2c60a4f710259db01b5"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 4: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-amd64-boringcrypto has failed with summary (view all results):

---

FAILURE

• go on master (change 578516)

Tests failed. See all test results.

Error: shard 1: failed to run "go tool dist test -json": exit status 1

Links:

• shard 1 build page
• shard 1 test results
• shard 1 "go tool dist test -json" (combined output)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result-1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

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

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

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.

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 5: Commit-Queue+1 Run-TryBot+1

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 5:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-04-13T06:45:31Z","revision":"8105df94bbbdcea6c9dd12e1ab293424d4db61ee"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 5:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Gopher Robot:

Patch Set 5:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

This PR (HEAD: 423f7fe) has been imported to Gerrit for code review.

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

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.

[gopherbot]

Message from Filippo Valsorda:

Patch Set 12:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 12:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 12:

(1 comment)

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

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

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

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.

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 13: Commit-Queue+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2024-05-22T15:54:17Z","revision":"7a449ef9ec03521ff37a753afba8a967fd31e3de"}

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Mateusz Poliwczak:

Patch Set 13: -Commit-Queue

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13:

This CL has passed the run

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[gopherbot]

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result+1

---

Please don’t reply on this GitHub thread. Visit golang.org/cl/578516.
After addressing review feedback, remember to publish your drafts!

[mateusz834]

Closing in favour of CL 602498