# \`move\` operator for ergonomic captures

**URL:** https://internals.rust-lang.org/t/move-operator-for-ergonomic-captures/21088
**Category:** language design
**Created:** [June 27, 2024, 12:10am UTC](https://internals.rust-lang.org/t/move-operator-for-ergonomic-captures/21088 "2024-06-27T00:10:57Z")
**Posts on this page:** 1
**Showing post:** 10

<div class="post-metadata">

### Author: ![bjorn3](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/bjorn3/32/2736_2.png) [@bjorn3](https://internals.rust-lang.org/u/bjorn3)
#### Post date: [June 27, 2024, 7:34am UTC](https://internals.rust-lang.org/t/move-operator-for-ergonomic-captures/21088/10 "2024-06-27T07:34:28Z")

</div>

Rather than a postfix `.move`, I think making it a block like `move {}` would make it clearer which code would be moved out of the closure body and makes it less likely to attempt to use a variable only defined inside the closure inside the `move {}` block.

---

_[View the full topic](https://internals.rust-lang.org/t/move-operator-for-ergonomic-captures/21088)._