aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-06-30 06:27:54 +0000
committerChris Lattner <sabre@nondot.org>2009-06-30 06:27:54 +0000
commita44f87f2e778a6d1adad56f5c44161b42aeb0b3a (patch)
tree8a96e9e56a0498c28b8c35d32639f0f4fb1c92b5
parent09bc65e62bb157141f0d3c6bc9c3f23cc4f83050 (diff)
got confused again
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@74514 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/CodingStandards.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/CodingStandards.html b/docs/CodingStandards.html
index ff29b39d6b..dbe95a8d58 100644
--- a/docs/CodingStandards.html
+++ b/docs/CodingStandards.html
@@ -709,7 +709,7 @@ at the start of the loop. In this case, the cost is probably minor: a few extra
loads every time through the loop. However, if the base expression is more
complex, then the cost can rise quickly. I've seen loops where the end
expression was actually something like: "<tt>SomeMap[x]->end()</tt>" and map
-lookups really aren't cheap. By writing it in the first form consistently, you
+lookups really aren't cheap. By writing it in the second form consistently, you
eliminate the issue entirely and don't even have to think about it.</p>
<p>The second (even bigger) issue is that writing the loop in the first form