diff options
| author | Steve Klabnik <steve@steveklabnik.com> | 2015-03-23 14:47:14 -0400 |
|---|---|---|
| committer | Steve Klabnik <steve@steveklabnik.com> | 2015-03-23 14:47:14 -0400 |
| commit | 05c9728c6943bc313e29cdf8140caecda0c62715 (patch) | |
| tree | a9a58cca51981fde331944f8fcce2b39a3775a44 | |
| parent | b0aad7dd4fad8d7e2e2f877a511a637258949597 (diff) | |
| download | rust-05c9728c6943bc313e29cdf8140caecda0c62715.tar.gz rust-05c9728c6943bc313e29cdf8140caecda0c62715.zip | |
Don't conflate regions and affine types
Fixes #23642
| -rw-r--r-- | src/doc/trpl/pointers.md | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/src/doc/trpl/pointers.md b/src/doc/trpl/pointers.md index 39106aaf857..bd9b449fc08 100644 --- a/src/doc/trpl/pointers.md +++ b/src/doc/trpl/pointers.md @@ -498,13 +498,10 @@ they go out of scope: However, boxes do _not_ use reference counting or garbage collection. Boxes are what's called an *affine type*. This means that the Rust compiler, at compile time, determines when the box comes into and goes out of scope, and inserts the -appropriate calls there. Furthermore, boxes are a specific kind of affine type, -known as a *region*. You can read more about regions [in this paper on the -Cyclone programming -language](http://www.cs.umd.edu/projects/cyclone/papers/cyclone-regions.pdf). +appropriate calls there. -You don't need to fully grok the theory of affine types or regions to grok -boxes, though. As a rough approximation, you can treat this Rust code: +You don't need to fully grok the theory of affine types to grok boxes, though. +As a rough approximation, you can treat this Rust code: ```{rust} { |
