Skip to content

Commit

Permalink
extern crate and mod are not easily confused
Browse files Browse the repository at this point in the history
Remove some statements that used to refer to similarities between `mod` and
`extern mod`, before the latter was renamed to `extern crate`.
  • Loading branch information
mbrubeck authored and alexcrichton committed Apr 3, 2014
1 parent 2ae2924 commit c1e52c7
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions src/doc/tutorial.md
Expand Up @@ -2600,8 +2600,6 @@ As you can see, your module hierarchy is now three modules deep: There is the cr
function, and the module `farm`. The module `farm` also contains two functions and a third module `barn`,
which contains a function `hay`.

(In case you already stumbled over `extern crate`: It isn't directly related to a bare `mod`, we'll get to it later. )

## Paths and visibility

We've now defined a nice module hierarchy. But how do we access the items in it from our `main` function?
Expand Down Expand Up @@ -3050,7 +3048,6 @@ fn main() {
}
~~~

Despite its name, `extern crate` is a distinct construct from regular `mod` declarations:
A statement of the form `extern crate foo;` will cause `rustc` to search for the crate `foo`,
and if it finds a matching binary it lets you use it from inside your crate.

Expand Down

0 comments on commit c1e52c7

Please sign in to comment.