mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor change.

Browse Source
This commit is contained in:
Sandeep Datta 2016-02-11 19:44:33 +05:30
parent 50d179e062
commit a8fd1bbd2f
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -171,10 +171,10 @@ v2.truncate(2);
and `v1` were still accessible we'd end up with an invalid vector since it
would not know that the heap data has been truncated. Now, the part of the
vector `v1` on the stack does not agree with its corresponding part on the
vector `v1` 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
happily let us access the non existent element `v1[2]` but as you might
already know this is a recipe for disaster.
already know this is a recipe for disaster (might lead to a segfault).
This is why Rust forbids using `v` after we’ve done the move.