OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Rollup merge of #33035 - jbranchaud:use-consistent-variable-names-in-ownership, r=GuillaumeGomez

Browse Source 
Use `v` instead of `v1` for consistency

The code examples and previous paragraphs all use `v` and `v2`
This commit is contained in:
Steve Klabnik 2016-04-18 14:50:35 -04:00
commit 31374d8030
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/doc/book/ownership.md
View File

@ -173,11 +173,11 @@ For example if we truncated the vector to just two elements through `v2`:
v2.truncate(2); v2.truncate(2);
``` ```
and `v1` were still accessible we'd end up with an invalid vector since `v1` and `v` were still accessible we'd end up with an invalid vector since `v`
would not know that the heap data has been truncated. Now, the part of the would not know that the heap data has been truncated. Now, the part of the
vector `v1` on the stack does not agree with the corresponding part on the vector `v` on the stack does not agree with the corresponding part on the
heap. `v1` still thinks there are three elements in the vector and will heap. `v` still thinks there are three elements in the vector and will
happily let us access the non existent element `v1[2]` but as you might happily let us access the non existent element `v[2]` but as you might
already know this is a recipe for disaster. Especially because it might lead already know this is a recipe for disaster. Especially because it might lead
to a segmentation fault or worse allow an unauthorized user to read from to a segmentation fault or worse allow an unauthorized user to read from
memory to which they don't have access. memory to which they don't have access.