about summary refs log tree commit diff
diff options
context:
space:
mode:
author4gboframram <79847791+4gboframram@users.noreply.github.com>2023-03-26 12:48:01 -0400
committerNilstrieb <48135649+Nilstrieb@users.noreply.github.com>2023-10-02 20:07:14 +0200
commit44c9818993d1ec5e7e6debdbb33ed2139341b60f (patch)
tree0bf3514b76a1d47629fe65b3d4c3e0826c2a4417
parent89c2e3d3d75486e52473de3ae38f0ca6efeffef2 (diff)
downloadrust-44c9818993d1ec5e7e6debdbb33ed2139341b60f.tar.gz
rust-44c9818993d1ec5e7e6debdbb33ed2139341b60f.zip
Improve wording of `hint::black_box` docs
The wording is a bit confusing.

Co-authored-by: Chris Denton <christophersdenton@gmail.com>
-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 a205565773a..285b5d8a631 100644
--- a/library/core/src/hint.rs
+++ b/library/core/src/hint.rs
@@ -287,7 +287,7 @@ pub fn spin_loop() {
 /// - Treats the call to `contains` and its result as volatile: the body of `benchmark` cannot
 ///   optimize this away
 ///
-/// This makes our benchmark much more realistic to how the function would be used in situ, where
+/// This makes our benchmark much more realistic to how the function would actually be used, where
 /// arguments are usually not known at compile time and the result is used in some way.
 #[inline]
 #[stable(feature = "bench_black_box", since = "1.66.0")]