diff options
| author | Brian Anderson <banderson@mozilla.com> | 2012-09-26 18:54:36 -0700 |
|---|---|---|
| committer | Brian Anderson <banderson@mozilla.com> | 2012-09-26 18:54:47 -0700 |
| commit | ae1a73029ce422ccd52c3c659a32c19ac60d0d4e (patch) | |
| tree | 9aec21f5ad87c671fd61c1275eb171841bf94018 /doc/tutorial.md | |
| parent | 1880d783b73387c1baac9e5cb0167d7a0f6e768c (diff) | |
| download | rust-ae1a73029ce422ccd52c3c659a32c19ac60d0d4e.tar.gz rust-ae1a73029ce422ccd52c3c659a32c19ac60d0d4e.zip | |
tutorial: Minor tweaks
Diffstat (limited to 'doc/tutorial.md')
| -rw-r--r-- | doc/tutorial.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tutorial.md b/doc/tutorial.md index ade15ebbc13..beebac6ed89 100644 --- a/doc/tutorial.md +++ b/doc/tutorial.md @@ -957,7 +957,7 @@ Rust has three competing goals that inform its view of memory: Most languages that offer strong memory safety guarantees rely upon a garbage-collected heap to manage all of the objects. This approach is straightforward both in concept and in implementation, but has -significant costs. Languages that take this approach tend to +significant costs. Languages that follow this path tend to aggressively pursue ways to ameliorate allocation costs (think the Java Virtual Machine). Rust supports this strategy with _managed boxes_: memory allocated on the heap whose lifetime is managed @@ -982,7 +982,7 @@ tasks. Experience in other languages has proven that isolating each task's heap from the others is a reliable strategy and one that is easy for programmers to reason about. Heap isolation has the additional benefit that garbage collection must only be done -per-heap. Rust never "stops the world" to garbage-collect memory. +per-heap. Rust never "stops the world" to reclaim memory. Complete isolation of heaps between tasks implies that any data transferred between tasks must be copied. While this is a fine and |
