What is the difference between `|_| async move {}` and `async move |_| {}`

by

One is the async block (a closure with async block as its body to be precise), while the other is async closure. Per async/await RFC:

async || closures

In addition to functions, async can also be applied to closures. Like an async function, an async closure has a return type of impl Future<Output = T>, rather than T.

On the other hand:

async blocks

You can create a future directly as an expression using an async block. This form is almost equivalent to an immediately-invoked async closure:

 async { /* body */ }

 // is equivalent to

 (async || { /* body */ })()

except that control-flow constructs like return, break and continue are not allowed within body.

The move keyword here is to denote that the async closure and block are to capture ownership of the variables they close over.

And apparently, async closure is still deemed to be unstable. It has this tracking issue.

More Related Contents:

  1. How to transform fields during deserialization using Serde?
  2. How is there a conflicting implementation of `From` when using a generic type?
  3. Temporarily move out of borrowed content
  4. Need holistic explanation about Rust’s cell and reference counted types
  5. Sending trait objects between threads in Rust
  6. Error while trying to borrow 2 fields from a struct wrapped in RefCell
  7. How to initialize struct fields which reference each other
  8. “Expected fn item, found a different fn item” when working with function pointers
  9. What does “mismatched types: expected `()`” mean when using an if expression?
  10. How do I read the entire body of a Tokio-based Hyper request?
  11. How can I downcast from Box to a trait object type?
  12. How do I ‘pass down’ feature flags to subdependencies in Cargo?
  13. When returning the outcome of consuming a StdinLock, why was the borrow to stdin retained?
  14. How does Rust pattern matching determine if the bound variable will be a reference or a value?
  15. Using generic trait methods like .into() when type inference is impossible
  16. Why does an enum require extra memory size?
  17. What is a crate attribute and where do I add it?
  18. Parameter type may not live long enough?
  19. Why does Rust disallow mutable aliasing?
  20. How to store rusqlite Connection and Statement objects in the same struct in Rust? [duplicate]
  21. How to model complex recursive data structures (graphs)?
  22. Why can’t I reuse a &mut reference after passing it to a function that accepts a generic type?
  23. print! macro not executed until pressing Enter
  24. How do I specify the linker path in Rust?
  25. How can I override a constant via a compiler option?
  26. Why am I getting “parameter is never used [E0392]”?
  27. Why does the Rust compiler request I constrain a generic type parameter’s lifetime (error E0309)?
  28. How do I create a HashMap with type erased keys?
  29. How to print structs and arrays?
  30. Can Rust optimise away the bit-wise copy during move of an object someday?

Leave a Comment