diff options
| author | Ben Striegel <ben.striegel@gmail.com> | 2014-01-22 16:03:00 -0500 |
|---|---|---|
| committer | Ben Striegel <ben.striegel@gmail.com> | 2014-01-22 16:03:00 -0500 |
| commit | fce792249e72a181f2ad52413b25b1db643c371f (patch) | |
| tree | 726bc94e51d0703fc456f2db45c41d364eda53f0 | |
| parent | aedf567a950a22acd183da6b1dd7a7fef92e8351 (diff) | |
| download | rust-fce792249e72a181f2ad52413b25b1db643c371f.tar.gz rust-fce792249e72a181f2ad52413b25b1db643c371f.zip | |
Typo in module tutorial
| -rw-r--r-- | doc/tutorial.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/tutorial.md b/doc/tutorial.md index 057944484ba..cc8dd6edd3f 100644 --- a/doc/tutorial.md +++ b/doc/tutorial.md @@ -3071,7 +3071,8 @@ The effect it has on your module hierarchy mirrors aspects of both `mod` and `us The linkage information the binary needs to use the library `foo`. - But like `use`, all `extern mod` statements that refer to the same library are interchangeable, - as each one really just presents an alias to an external module (the crate root of the library your linking against). + as each one really just presents an alias to an external module (the crate root of the library + you're linking against). Remember how `use`-statements have to go before local declarations because the latter shadows the former? Well, `extern mod` statements also have their own rules in that regard: |