Rollup merge of #25195 - simonkern:master, r=steveklabnik
I deleted one unneccessary 'the' and added the href for [bindings]
This commit is contained in:
commit
4b4cb86248
3 changed files with 5 additions and 4 deletions
|
@ -116,7 +116,7 @@ fn main() {
|
||||||
}
|
}
|
||||||
```
|
```
|
||||||
|
|
||||||
[struct]: structs.html
|
[structs]: structs.html
|
||||||
|
|
||||||
As you can see, `struct`s can also have lifetimes. In a similar way to functions,
|
As you can see, `struct`s can also have lifetimes. In a similar way to functions,
|
||||||
|
|
||||||
|
|
|
@ -3,7 +3,7 @@
|
||||||
This guide is one of three presenting Rust’s ownership system. This is one of
|
This guide is one of three presenting Rust’s ownership system. This is one of
|
||||||
Rust’s most unique and compelling features, with which Rust developers should
|
Rust’s most unique and compelling features, with which Rust developers should
|
||||||
become quite acquainted. Ownership is how Rust achieves its largest goal,
|
become quite acquainted. Ownership is how Rust achieves its largest goal,
|
||||||
memory safety. The there are a few distinct concepts, each with its own
|
memory safety. There are a few distinct concepts, each with its own
|
||||||
chapter:
|
chapter:
|
||||||
|
|
||||||
* ownership, which you’re reading now.
|
* ownership, which you’re reading now.
|
||||||
|
@ -59,6 +59,7 @@ deterministically, at the end of the scope.
|
||||||
|
|
||||||
[vect]: ../std/vec/struct.Vec.html
|
[vect]: ../std/vec/struct.Vec.html
|
||||||
[heap]: the-stack-and-the-heap.html
|
[heap]: the-stack-and-the-heap.html
|
||||||
|
[bindings]: variable-bindings.html
|
||||||
|
|
||||||
# Move semantics
|
# Move semantics
|
||||||
|
|
||||||
|
@ -122,7 +123,7 @@ let v2 = v;
|
||||||
|
|
||||||
The first line creates some data for the vector on the [stack][sh], `v`. The
|
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
|
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
|
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
|
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
|
introducing a data race. Therefore, Rust forbids using `v` after we’ve done the
|
||||||
|
|
|
@ -3,7 +3,7 @@
|
||||||
This guide is one of three presenting Rust’s ownership system. This is one of
|
This guide is one of three presenting Rust’s ownership system. This is one of
|
||||||
Rust’s most unique and compelling features, with which Rust developers should
|
Rust’s most unique and compelling features, with which Rust developers should
|
||||||
become quite acquainted. Ownership is how Rust achieves its largest goal,
|
become quite acquainted. Ownership is how Rust achieves its largest goal,
|
||||||
memory safety. The there are a few distinct concepts, each with its own
|
memory safety. There are a few distinct concepts, each with its own
|
||||||
chapter:
|
chapter:
|
||||||
|
|
||||||
* [ownership][ownership], ownership, the key concept
|
* [ownership][ownership], ownership, the key concept
|
||||||
|
|
Loading…
Add table
Reference in a new issue