about summary refs log tree commit diff
path: root/src
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2014-09-10 18:24:40 -0400
committerSteve Klabnik <steve@steveklabnik.com>2014-09-10 18:24:40 -0400
commitb85191ae0f9bbef40fea18796d7a134e2f505588 (patch)
tree4cfe7c46d1070f3588ea429fe021597226cd0ec5 /src
parent651106462c357b71a4ca2c02ba2bfedfc38b0035 (diff)
downloadrust-b85191ae0f9bbef40fea18796d7a134e2f505588.tar.gz
rust-b85191ae0f9bbef40fea18796d7a134e2f505588.zip
dave hates jokes :wink:
Diffstat (limited to 'src')
-rw-r--r--src/doc/guide.md5
1 files changed, 1 insertions, 4 deletions
diff --git a/src/doc/guide.md b/src/doc/guide.md
index 6d0fd54cd4c..3cac1b4f4de 100644
--- a/src/doc/guide.md
+++ b/src/doc/guide.md
@@ -1326,10 +1326,7 @@ upper bound is exclusive, though, so our loop will print `0` through `9`, not
 
 Rust does not have the "C style" `for` loop on purpose. Manually controlling
 each element of the loop is complicated and error prone, even for experienced C
-developers. There's an old joke that goes, "There are two hard problems in
-computer science: naming things, cache invalidation, and off-by-one errors."
-The joke, of course, being that the setup says "two hard problems" but then
-lists three things. This happens quite a bit with "C style" `for` loops.
+developers. 
 
 We'll talk more about `for` when we cover **iterator**s, later in the Guide.