fix off-by-one error

[bmusin]

Fixes #47325.

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @joshtriplett (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. Due to 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.

[steveklabnik]

Nice catch, thank you!

@bors: r+ rollup

[bors]

📌 Commit 0e9dde9 has been approved by steveklabnik

[nixpulvis]

Maybe use an inclusive range to be more clear?

[bmusin]

@nixpulvis, you mean 0..10?

[nixpulvis]

Nope, though now that I'm playing with it it looks like it's experamental and kinda a mess imho, see #28237.

Inclusive ranges (in this context) include the last element as well as the rest.

[nixpulvis]

I would however strongly encourage a change to 0..10, since it's helpful to have the same number in the description and the code.

[varkor]

This change is now incorrect. The documentation says:

Let's write the numbers one through ten to a [TcpStream]:

The code now writes the numbers from zero through nine. You should add one to i in each case. (This will be cleaner with the inclusive range syntax, but as it's not stabilised yet, it's best not to include it.)

[bmusin]

@varkor, you meant this?

[nixpulvis]

@varkor oh nice catch, I should have read the docs more carefully before suggesting 0..10. Still I think this looks the best.

[shepmaster]

Looks great @bmusin! Please go ahead and squash these commits and we will be good to merge!

[bmusin]

Squashed.

[shepmaster]

Thanks!

@bors: r+ rollup

[bors]

📌 Commit cee295e has been approved by shepmaster