From a2f6d294202764e3d951054b42955c568e3a306b Mon Sep 17 00:00:00 2001 From: Tang Chenglong Date: Sat, 2 Apr 2016 21:03:59 +0800 Subject: [PATCH] Remove error description of `move` (1) `x` can be used in main() after the call to spawn(). Because the variables follow normal move semantics, though the keyword `move` is used, and i32 implements `Copy`. (2) I remove this sentence because the previous sentence gives the referrence to `move closures`, and more description of `move` may be redundant. --- src/doc/book/concurrency.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/doc/book/concurrency.md b/src/doc/book/concurrency.md index 87d551b68df07..d90b7e3eaf081 100644 --- a/src/doc/book/concurrency.md +++ b/src/doc/book/concurrency.md @@ -127,9 +127,7 @@ thread may outlive the scope of `x`, leading to a dangling pointer. To fix this, we use a `move` closure as mentioned in the error message. `move` closures are explained in depth [here](closures.html#move-closures); basically -they move variables from their environment into themselves. This means that `x` -is now owned by the closure, and cannot be used in `main()` after the call to -`spawn()`. +they move variables from their environment into themselves. ```rust use std::thread;