From 72c1a6fbb8d116178ad7a0ae98d5c57ff063bac2 Mon Sep 17 00:00:00 2001 From: 4gboframram <79847791+4gboframram@users.noreply.github.com> Date: Sun, 26 Mar 2023 12:48:01 -0400 Subject: [PATCH] Improve wording of `hint::black_box` docs The wording is a bit confusing. Co-authored-by: 4gboframram <79847791+4gboframram@users.noreply.github.com> Co-authored-by: Chris Denton --- library/core/src/hint.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/core/src/hint.rs b/library/core/src/hint.rs index a205565773a71..285b5d8a6313d 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")]