# Unsafe Impl Copy and Freeze

**URL:** <https://internals.rust-lang.org/t/unsafe-impl-copy-and-freeze/21729>\
**Category:** language design\
**Created:** [October 20, 2024, 2:32am UTC](https://internals.rust-lang.org/t/unsafe-impl-copy-and-freeze/21729 "2024-10-20T02:32:05Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![soundlogic2236](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/soundlogic2236/32/10367_2.png) [@soundlogic2236](https://internals.rust-lang.org/u/soundlogic2236)\
**Post date:** [October 20, 2024, 5:11am UTC](https://internals.rust-lang.org/t/unsafe-impl-copy-and-freeze/21729/7 "2024-10-20T05:11:59Z")

</div>

OK according to [A type that is sometimes Drop and sometimes Copy: is this even theoretically possible?](https://internals.rust-lang.org/t/a-type-that-is-sometimes-drop-and-sometimes-copy-is-this-even-theoretically-possible/14234) it is actually maybe already possible at least in some cases using the (also very unsafe) specialization system.

Note "values of type T never execute any code when dropped" if weakened to "have no side effects when dropped" would be fulfilled by the example `MyOption`, though I suppose even low but present side effect level things like panics could mess up unsafe code.

---

_[View the full topic](https://internals.rust-lang.org/t/unsafe-impl-copy-and-freeze/21729)._
