about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2023-03-26 08:39:28 +0200
committerGitHub <noreply@github.com>2023-03-26 08:39:28 +0200
commit776a8f4ecae4292b064987f10b01b4e2e81fc2f4 (patch)
tree21bdb7a7ccb7a0daf1cc8c5c08d8d9ffb89055d3
parent705435fe0115e6a56112cbf4cbe8cb51bf061a18 (diff)
parent323551abb1e4a34a9e9e81ebcc49e5224af8a5cb (diff)
downloadrust-776a8f4ecae4292b064987f10b01b4e2e81fc2f4.tar.gz
rust-776a8f4ecae4292b064987f10b01b4e2e81fc2f4.zip
Rollup merge of #109620 - eievui5:patch-1, r=compiler-errors
Correct typo (`back_box` -> `black_box`)
-rw-r--r--library/core/src/hint.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/hint.rs b/library/core/src/hint.rs
index ee13dae60b1..a205565773a 100644
--- a/library/core/src/hint.rs
+++ b/library/core/src/hint.rs
@@ -228,7 +228,7 @@ pub fn spin_loop() {
 /// This _immediately_ precludes any direct use of this function for cryptographic or security
 /// purposes.
 ///
-/// While not suitable in those mission-critical cases, `back_box`'s functionality can generally be
+/// While not suitable in those mission-critical cases, `black_box`'s functionality can generally be
 /// relied upon for benchmarking, and should be used there. It will try to ensure that the
 /// compiler doesn't optimize away part of the intended test code based on context. For
 /// example: