Added an example of slicing result #2649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should make it clearer how slicing works.
Context: I woke up recently with my head hurting and wanted to do some coding in Rust. Strangely, despite years of Rust experience I couldn't remember whether
arr[a..b].len() == b
orarr[a..b].len() == b - a
and surprisingly I couldn't find quick and clear answer that my hurting head could understand.It seems that almost everyone including me does
[..pos]
and[pos..]
most of the time until we don't... Yes, I know I shouldn't probably do coding in my mental state and maybe not even contribute but I love this language too much to stay quiet when I see something missing in the docs...