From f539c416a0ef87c645de26b67e01a047afcb0b2a Mon Sep 17 00:00:00 2001 From: David Reid Date: Wed, 13 May 2015 20:41:03 -0700 Subject: [PATCH] Fix automatic substitution of task->thread. --- src/doc/trpl/iterators.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/doc/trpl/iterators.md b/src/doc/trpl/iterators.md index e0cc45c254b99..a93f622e9c529 100644 --- a/src/doc/trpl/iterators.md +++ b/src/doc/trpl/iterators.md @@ -42,7 +42,7 @@ loop is just a handy way to write this `loop`/`match`/`break` construct. `for` loops aren't the only thing that uses iterators, however. Writing your own iterator involves implementing the `Iterator` trait. While doing that is outside of the scope of this guide, Rust provides a number of useful iterators -to accomplish various threads. Before we talk about those, we should talk about a +to accomplish various tasks. Before we talk about those, we should talk about a Rust anti-pattern. And that's using ranges like this. Yes, we just talked about how ranges are cool. But ranges are also very