Uh oh!
There was an error while loading. Please reload this page.
Update ops range example to avoid confusion between indexes and values. - #48151
Conversation
rust-highfive
commented
Feb 12, 2018
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @BurntSushi (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. |
estebank
commented
Feb 12, 2018
@bors r+ rollup |
bors
commented
Feb 12, 2018
📌 Commit bd426f1 has been approved by |
…=estebank Update ops range example to avoid confusion between indexes and values. Makes clearer the numbers in the range refer to indexes, not the values at those indexes.
…=estebank Update ops range example to avoid confusion between indexes and values. Makes clearer the numbers in the range refer to indexes, not the values at those indexes.
…=estebank Update ops range example to avoid confusion between indexes and values. Makes clearer the numbers in the range refer to indexes, not the values at those indexes.
echochamber
commented
Feb 14, 2018
@estebank Looks like bors has rolled this up. Should I close this PR? |
estebank
commented
Feb 14, 2018
@echochamber leave it, the rollup PR hasn't been merged yet. Once it gets merged, this PR will get closed automatically. |
echochamber
commented
Feb 15, 2018
Sounds good. Thanks. |
Makes clearer the numbers in the range refer to indexes, not the values at those indexes.