github_mirrors/rust-book-cn
1
0
Fork 0
mirror of https://github.com/rust-lang-cn/book-cn.git synced 2025-02-03 07:48:41 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fix references that are now invalid with the rearranging

Browse Source
This commit is contained in:
Carol (Nichols || Goulding) 2016-07-14 14:39:32 -04:00
parent 35bb02632c
commit 72ec43263b
2 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
src/ch04-01-understanding-ownership.md
View File

@ -1,6 +1,5 @@
# Understanding Ownership # Understanding Ownership
Now that we’ve got some basic syntax under our belt, it’s time to take a look Now let's look at Rust’s most unique feature: ownership. We’ll also talk about
at Rust’s most unique feature: ownership. We’ll also talk about several related several related features: borrowing, slices, and lifetimes, as well as how Rust
features: borrowing, slices, and lifetimes, as well as how Rust lays things out lays things out in memory.
in memory.

5
src/ch04-02-ownership.md
View File

@ -168,11 +168,6 @@ the `String` is currently using. The capacity is the total amount of memory the
and capacity matters, but not in this context, so don’t worry about it too much and capacity matters, but not in this context, so don’t worry about it too much
if it doesn’t make sense, and just ignore the capacity. if it doesn’t make sense, and just ignore the capacity.
> We’ve talked about two kinds of composite types: arrays and tuples. `String`
> is a third type: a `struct`, which we will cover the details of in the next
> chapter of the book. For now, thinking about `String` as a tuple is close
> enough.
When we assign `s1` to `s2`, the `String` itself is copied. But not all kinds When we assign `s1` to `s2`, the `String` itself is copied. But not all kinds
of copying are the same. Many people draw distinctions between ‘shallow of copying are the same. Many people draw distinctions between ‘shallow
copying’ and ‘deep copying’. We don’t use these terms in Rust. We instead say copying’ and ‘deep copying’. We don’t use these terms in Rust. We instead say