# Impossible to have a container that is either Copy or Drop depending on T?

**URL:** <https://users.rust-lang.org/t/impossible-to-have-a-container-that-is-either-copy-or-drop-depending-on-t/56608>\
**Category:** uncategorized\
**Created:** [March 7, 2021, 3:55pm UTC](https://users.rust-lang.org/t/impossible-to-have-a-container-that-is-either-copy-or-drop-depending-on-t/56608 "2021-03-07T15:55:15Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![H2CO3](https://avatars.discourse-cdn.com/v4/letter/h/b5ac83/32.png) [@H2CO3](https://users.rust-lang.org/u/H2CO3)\
**Post date:** [March 7, 2021, 5:25pm UTC](https://users.rust-lang.org/t/impossible-to-have-a-container-that-is-either-copy-or-drop-depending-on-t/56608/6 "2021-03-07T17:25:49Z")

</div>

> [@jgarvin](#):
>
> why explicitly prohibit people

It isn't "explicitly prohibiting", it's a limitation of the type system. I'm not sure if it's possible to alleviate this problem, but there exist workarounds (for which you explicitly asked for, hence my answers).

---

_[View the full topic](https://users.rust-lang.org/t/impossible-to-have-a-container-that-is-either-copy-or-drop-depending-on-t/56608)._