From 88d7f0a8daf9c147178e4ea2b1815f6a035ccaa2 Mon Sep 17 00:00:00 2001 From: Daniel Hofstetter Date: Sat, 1 Nov 2014 14:56:48 +0100 Subject: [PATCH] Guide: Fix variable name --- src/doc/guide-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/guide-testing.md b/src/doc/guide-testing.md index 9d15f55f33f6..4128ae9538b6 100644 --- a/src/doc/guide-testing.md +++ b/src/doc/guide-testing.md @@ -287,7 +287,7 @@ The benchmarking runner offers two ways to avoid this. Either, the closure that the `iter` method receives can return an arbitrary value which forces the optimizer to consider the result used and ensures it cannot remove the computation entirely. This could be done for the -example above by adjusting the `bh.iter` call to +example above by adjusting the `b.iter` call to ~~~ # struct X; impl X { fn iter(&self, _: || -> T) {} } let b = X;