---

yaml
---
r: 15336
b: refs/heads/try
c: fc7fc90
h: refs/heads/master
v: v3

Author: catamorphism

[refs]

@@ -2,5 +2,5 @@
 refs/heads/master: 61b1875c16de39c166b0f4d54bba19f9c6777d1a
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 4a81779abd786ff22d71434c6d9a5917ea4cdfff
-refs/heads/try: b91c9f803d3b87be3c6b7480ef9abbd9611c717c
+refs/heads/try: fc7fc90adfc9576507e730ab54f35d1073ab2a4f
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105

branches/try/doc/tutorial.md

@@ -1686,6 +1686,7 @@ purpose, you create a `.rc` crate file, which references any number of
 
 ~~~~ {.ignore}
 #[link(name = "farm", vers = "2.5", author = "mjh")];
+#[crate_type = "lib"];
 mod cow;
 mod chicken;
 mod horse;
@@ -1694,7 +1695,9 @@ mod horse;
 Compiling this file will cause `rustc` to look for files named
 `cow.rs`, `chicken.rs`, `horse.rs` in the same directory as the `.rc`
 file, compile them all together, and, depending on the presence of the
-`--lib` switch, output a shared library or an executable.
+`crate_type = "lib"` attribute, output a shared library or an executable.
+(If the line `#[crate_type = "lib"];` was omitted, `rustc` would create an
+executable.)
 
 The `#[link(...)]` part provides meta information about the module,
 which other crates can use to load the right module. More about that
@@ -1717,9 +1720,9 @@ content to the `poultry` module itself.
 
 ## Using other crates
 
-Having compiled a crate with `--lib`, you can use it in another crate
-with a `use` directive. We've already seen `use std` in several of the
-examples, which loads in the [standard library][std].
+Having compiled a crate that contains the `#[crate_type = "lib"]` attribute,
+you can use it in another crate with a `use` directive. We've already seen
+`use std` in several of the examples, which loads in the [standard library][std].
 
 [std]: http://doc.rust-lang.org/doc/std/index/General.html