aboutsummaryrefslogtreecommitdiffstats
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
commit088affa60c5db3e53008dc5a260b507f190f69cf (patch)
tree8a96e9e56a0498c28b8c35d32639f0f4fb1c92b5
parentdc43b3424bb2b1b8b8b9cebf1986231ce4e53cd2 (diff)
downloadexternal_llvm-088affa60c5db3e53008dc5a260b507f190f69cf.zip
external_llvm-088affa60c5db3e53008dc5a260b507f190f69cf.tar.gz
external_llvm-088affa60c5db3e53008dc5a260b507f190f69cf.tar.bz2
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 ff29b39..dbe95a8 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