about summary refs log tree commit diff
diff options
context:
space:
mode:
authorBrian Anderson <banderson@mozilla.com>2012-07-06 14:52:21 -0700
committerBrian Anderson <banderson@mozilla.com>2012-07-06 14:52:21 -0700
commitea4cd49e9f81389bb4f709df17810b0dff3a918a (patch)
tree64ffd29d52ea46914690c3fcac67bf8c54dd9e18
parent82001412f2a454158d8e29d7d1a4d1122e734e57 (diff)
tutorial: Minor tweak
-rw-r--r--doc/tutorial.md13
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/tutorial.md b/doc/tutorial.md
index 7872a695827..b662a218eb4 100644
--- a/doc/tutorial.md
+++ b/doc/tutorial.md
@@ -926,13 +926,12 @@ memory. Even high-level languages frequently avoid solving this
 problem, requiring programmers to correctly employ locking to unsure
 their program is free of races.
 
-Rust solves this problem by starting from the position that memory
-simply cannot be shared between tasks. Experience in other languages
-has proven that isolating each tasks' heap from each other is
-a reliable strategy and one that is easy for programmers to reason
-about. Having isolated heaps additionally means that garbage collection
-must only be done per-heap. Rust never 'stops the world' to garbage
-collect memory.
+Rust starts from the position that memory simply cannot be shared
+between tasks. Experience in other languages has proven that isolating
+each tasks' heap from each other is a reliable strategy and one that
+is easy for programmers to reason about. Having isolated heaps
+additionally means that garbage collection must only be done
+per-heap. Rust never 'stops the world' to garbage collect memory.
 
 If Rust tasks have completely isolated heaps then that seems to imply
 that any data transferred between them must be copied. While this