Fix off by one in the iterator documentation

[stevegury]

(1..100).map(|x| x + 1) is actually mapping [1,100) to [2,101)

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pcwalton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[mitaa]

Are you sure? (Range has an exclusive upper bound)
http://doc.rust-lang.org/nightly/std/ops/struct.Range.html

println!("{:?}", (1..100).map(|x| x + 1).collect::<Vec<usize>>());
// [2, 3, 4, ... 98, 99, 100]

[mitaa]

I see.. the off by one error is a bit further up
http://doc.rust-lang.org/book/iterators.html#iterators

This code, for example, does not actually generate the numbers 1-100, instead creating a value that merely represents the sequence:

let nums = 1..100;

[stevegury]

@mitaa you're right, thanks for correcting me.
I updated the right off by one.

[steveklabnik]

@bors: r+ rollup

[bors]

📌 Commit bef9361 has been approved by steveklabnik

[bors]

⌛ Testing commit bef9361 with merge 60926b8...

[steveklabnik]

Thanks @stevegury !

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-gnu-32-nopt-t, auto-win-gnu-32-opt, auto-win-gnu-64-nopt-t, auto-win-gnu-64-opt