From 6a92cf9ace765a590991e4a1688164f4ed54194f Mon Sep 17 00:00:00 2001 From: ben fleis Date: Tue, 2 Jun 2015 22:55:39 +0200 Subject: [PATCH] Add note about expression vs. statement to dining philosphers problem, to address https://github.com/rust-lang/rust/issues/25488 . --- src/doc/trpl/dining-philosophers.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/doc/trpl/dining-philosophers.md b/src/doc/trpl/dining-philosophers.md index 7e37473ac8fea..a18d9bb442dd2 100644 --- a/src/doc/trpl/dining-philosophers.md +++ b/src/doc/trpl/dining-philosophers.md @@ -432,7 +432,9 @@ an extra annotation, `move`, to indicate that the closure is going to take ownership of the values it’s capturing. Primarily, the `p` variable of the `map` function. -Inside the thread, all we do is call `eat()` on `p`. +Inside the thread, all we do is call `eat()` on `p`. Also note that the call to `thread::spawn` lacks a trailing semicolon, making this an expression. This distinction is important, yielding the correct return value. For more details, read [Expressions vs. Statements][es]. + +[es]: functions.html#expressions-vs.-statements ```rust,ignore }).collect();