Ordering of async move keywords

rust-lang · withoutboats · May 8, 2018 · Apr 5, 2018 · Apr 9, 2018 · Apr 9, 2018
commit bcd934a59fc6c2c4f3b2e860c2a56aecbcf2b117
diff --git a/text/0000-async_await.md b/text/0000-async_await.md
@@ -119,6 +119,9 @@ fn main() {
 This will print both "Hello from main" statements before printing "Hello from
 async closure."
 
+`async` closures can be annotated with `move` to capture ownership of the
+variables they close over.
+
 ## `async` blocks
 
 You can create a future directly as an expression using an `async` block:
@@ -240,7 +243,7 @@ fn foo<'a>(arg1: &'a str, arg2: &str) -> impl Future<Output = usize> + 'a {
     // do some initialization using arg2
 
     // closure which is evaluated immediately
-    move async {
+    async move {
          // asynchronous portion of the function
     }
 }
@@ -265,6 +268,19 @@ This is not a literal expansion, because the `yield` concept cannot be
 expressed in the surface syntax within `async` functions. This is why `await!`
 is a compiler builtin instead of an actual macro.
 
+## The order of `async` and `move`
+
+Async closures and blocks can be annotated with `move` to capture ownership of
+the variables they close over. The order of the keywords is fixed to
+`async move`. Permitting only one ordering avoids confusion about whether it is
+significant for the meaning.
+
+```rust
+async move {
+    // body
+}
+```
+
 # Drawbacks
 [drawbacks]: #drawbacks