about summary refs log tree commit diff
diff options
context:
space:
mode:
authorSimon Kern <simon.kern@rwth-aachen.de>2015-05-08 01:43:18 +0200
committerSimon Kern <simon.kern@rwth-aachen.de>2015-05-08 01:43:18 +0200
commit3e76f2838a68d0669cef64477e7f39af1b6205f6 (patch)
treec797879948d121247d3d4913e05769203291d4cc
parent84c7dfa48c23dd032e4abd917706b5649067b311 (diff)
downloadrust-3e76f2838a68d0669cef64477e7f39af1b6205f6.tar.gz
rust-3e76f2838a68d0669cef64477e7f39af1b6205f6.zip
v2 gets a copy of the pointer, not a copy of the data
-rw-r--r--src/doc/trpl/ownership.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/trpl/ownership.md b/src/doc/trpl/ownership.md
index 1da21345aa4..fba5226ca2e 100644
--- a/src/doc/trpl/ownership.md
+++ b/src/doc/trpl/ownership.md
@@ -123,7 +123,7 @@ let v2 = v;
 
 The first line creates some data for the vector on the [stack][sh], `v`. The
 vector’s data, however, is stored on the [heap][sh], and so it contains a
-pointer to that data. When we move `v` to `v2`, it creates a copy of that data,
+pointer to that data. When we move `v` to `v2`, it creates a copy of that pointer,
 for `v2`. Which would mean two pointers to the contents of the vector on the
 heap. That would be a problem: it would violate Rust’s safety guarantees by
 introducing a data race. Therefore, Rust forbids using `v` after we’ve done the