OpenE2K/rust
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

tutorial: Minor tweaks

Browse Source
This commit is contained in:
Brian Anderson 2012-09-26 18:54:36 -07:00
parent 1880d783b7
commit ae1a73029c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/tutorial.md
View File

@ -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 Most languages that offer strong memory safety guarantees rely upon a
garbage-collected heap to manage all of the objects. This approach is garbage-collected heap to manage all of the objects. This approach is
straightforward both in concept and in implementation, but has 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 aggressively pursue ways to ameliorate allocation costs (think the
Java Virtual Machine). Rust supports this strategy with _managed Java Virtual Machine). Rust supports this strategy with _managed
boxes_: memory allocated on the heap whose lifetime is 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 task's heap from the others is a reliable strategy and one that is
easy for programmers to reason about. Heap isolation has the easy for programmers to reason about. Heap isolation has the
additional benefit that garbage collection must only be done 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 Complete isolation of heaps between tasks implies that any data
transferred between tasks must be copied. While this is a fine and transferred between tasks must be copied. While this is a fine and