about summary refs log tree commit diff
diff options
context:
space:
mode:
authorMatthias Bussonnier <bussonniermatthias@gmail.com>2015-11-24 21:58:18 +0100
committerMatthias Bussonnier <bussonniermatthias@gmail.com>2015-11-24 21:58:18 +0100
commit5aa45071db5d00137702e8dbde4af943dcff5de0 (patch)
tree4067fd430f3a2e6aa316b4232a7daa7428875400
parent1004860dd42632733d985bbf23bd12d0fd23badb (diff)
downloadrust-5aa45071db5d00137702e8dbde4af943dcff5de0.tar.gz
rust-5aa45071db5d00137702e8dbde4af943dcff5de0.zip
Add cargo instructions for dinning_philosopher project
At this point of the book, reader have likely use `cargo new --bin`,
likely 2 times, once if they are lazy. This remind them of the `cargo`
syntax.

I was myself unsure whether it was `cargo create`, `cargo new`, and
whether it would initialize in current working directory or needed a
target.
-rw-r--r--src/doc/book/dining-philosophers.md13
1 files changed, 11 insertions, 2 deletions
diff --git a/src/doc/book/dining-philosophers.md b/src/doc/book/dining-philosophers.md
index 50d758c3a10..ace0fbc821a 100644
--- a/src/doc/book/dining-philosophers.md
+++ b/src/doc/book/dining-philosophers.md
@@ -45,8 +45,17 @@ Now, let’s imagine this sequence of events:
 6. ... ? All the forks are taken, but nobody can eat!
 
 There are different ways to solve this problem. We’ll get to our solution in
-the tutorial itself. For now, let’s get started modeling the problem itself.
-We’ll start with the philosophers:
+the tutorial itself. For now, let’s get started and create a new project with
+`cargo`:
+
+```bash
+$ cd ~/projects
+$ cargo new dining_philosophers --bin
+$ cd dining_philosophers
+```
+
+Now we can start modeling the problem itself. We’ll start with the philosophers
+in `src/main.rs`:
 
 ```rust
 struct Philosopher {