From 3b9a9fce49d4c0ad5247ca04f2d2cb89ff8c001a Mon Sep 17 00:00:00 2001 From: Joe Pletcher Date: Wed, 25 Jan 2012 00:51:16 -0800 Subject: [PATCH] Remove reference to tags, replace enums. --- doc/tutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/tutorial.md b/doc/tutorial.md index 98b911bd4b0..390d5e3d95a 100644 --- a/doc/tutorial.md +++ b/doc/tutorial.md @@ -1346,7 +1346,7 @@ destructors. Resources might go away in the future. Rust datatypes are not trivial to copy (the way, for example, JavaScript values can be copied by simply taking one or two machine words and plunking them somewhere else). Shared boxes require -reference count updates, big records, tags, or unique pointers require +reference count updates, big records, enums, or unique pointers require an arbitrary amount of data to be copied (plus updating the reference counts of shared boxes hanging off them). @@ -1459,7 +1459,7 @@ alt my_rec { The fact that arguments are conceptually passed by safe reference does not mean all arguments are passed by pointer. Composite types like -records and tags *are* passed by pointer, but single-word values, like +records and enums *are* passed by pointer, but single-word values, like integers and pointers, are simply passed by value. Most of the time, the programmer does not have to worry about this, as the compiler will simply pick the most efficient passing style. There is one exception,