diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2015-06-12 11:55:37 +0530 |
|---|---|---|
| committer | Manish Goregaokar <manishsmail@gmail.com> | 2015-06-12 11:55:37 +0530 |
| commit | 18f70e3498bc3c947d060143850e5fe0bf7d0a4b (patch) | |
| tree | a21bb17c141c98645d11fdf39a0cbbf1a34d1afc | |
| parent | 69db64f3046b8c28fcc6a165e4a4fa45a430c51b (diff) | |
| parent | a47d7a752e8554dc3cc3667b1715d95a3848f620 (diff) | |
Rollup merge of #24495 - nathanl:nathanl-explain-bin-flag, r=steveklabnik
Explain the --bin flag in terms of the difference between shipping binary and library code I'm not sure if my explanation is even quite correct, but as a newbie coming from Ruby, this is my best guess. (In Rubyland, libraries always ship with the source code because there's no other form you can ship. :) )
| -rw-r--r-- | src/doc/trpl/hello-cargo.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/src/doc/trpl/hello-cargo.md b/src/doc/trpl/hello-cargo.md index 9920e8e0068..8e479977887 100644 --- a/src/doc/trpl/hello-cargo.md +++ b/src/doc/trpl/hello-cargo.md @@ -145,8 +145,7 @@ To start a new project with Cargo, use `cargo new`: $ cargo new hello_world --bin ``` -We’re passing `--bin` because we're making a binary program: if we were making -a library, we'd leave it off. +We’re passing `--bin` because our goal is to get straight to making an executable application, as opposed to a library. Executables are often called ‘binaries.’ (as in `/usr/bin`, if you’re on a Unix system) Let's check out what Cargo has generated for us: |