# Asynchronous Destructors

**URL:** <https://internals.rust-lang.org/t/asynchronous-destructors/11127>\
**Category:** Uncategorized\
**Created:** [October 16, 2019, 4:09pm UTC](https://internals.rust-lang.org/t/asynchronous-destructors/11127 "2019-10-16T16:09:27Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![CAD97](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/cad97/32/3460_2.png) [@CAD97](https://internals.rust-lang.org/u/CAD97)\
**Post date:** [October 16, 2019, 10:22pm UTC](https://internals.rust-lang.org/t/asynchronous-destructors/11127/16 "2019-10-16T22:22:52Z")

</div>

The ability to forget something is intrinsic to Rust at this point. If memory safety requires destructors, the two options are pinning and scopes.

`Pin` requires the destructor of a place to be run before invalidating it IIRC. Scopes like `crossbeam::scope` allow loaning of the space such that it cannot be forgotten in user code.

---

_[View the full topic](https://internals.rust-lang.org/t/asynchronous-destructors/11127)._
