From a8fd1bbd2f9511e9394fed1112c4ada186eb1b00 Mon Sep 17 00:00:00 2001 From: Sandeep Datta Date: Thu, 11 Feb 2016 19:44:33 +0530 Subject: [PATCH] Minor change. --- src/doc/book/ownership.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/doc/book/ownership.md b/src/doc/book/ownership.md index 5c603582bfc..63c0671e659 100644 --- a/src/doc/book/ownership.md +++ b/src/doc/book/ownership.md @@ -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.