nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-02-19 18:34:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fixed build error as per steveklabnik's suggestion and expanded on the ills of doing out of bounds accesses.

Browse Source
This commit is contained in:
Sandeep Datta 2016-02-13 18:40:24 +05:30
parent a6fedc85bf
commit 37a952a672
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -166,6 +166,8 @@ Rust’s safety guarantees by introducing a data race if one could access both
For example if we truncated the vector to just two elements through `v2`:
```rust
# let v = vec![1, 2, 3];
# let v2 = v;
v2.truncate(2);
```
@ -174,7 +176,9 @@ 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
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 (might lead to a segfault).
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
memory to which they don't have access.
This is why Rust forbids using `v` after we’ve done the move.