# Non-static data in \`static\`

**URL:** <https://internals.rust-lang.org/t/non-static-data-in-static/21247>\
**Category:** language design\
**Created:** [July 25, 2024, 11:33am UTC](https://internals.rust-lang.org/t/non-static-data-in-static/21247 "2024-07-25T11:33:45Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Ddystopia](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/ddystopia/32/10915_2.png) [@Ddystopia](https://internals.rust-lang.org/u/Ddystopia)\
**Post date:** [July 26, 2024, 9:36am UTC](https://internals.rust-lang.org/t/non-static-data-in-static/21247/6 "2024-07-26T09:36:03Z")

</div>

I've opened [What do we need to get the same functionality without `generic_const_exprs`?](https://internals.rust-lang.org/t/what-do-we-need-to-get-the-same-functionality-without-generic-const-exprs/21255) that elaborates the question. There is real unsafe implemention, but it requires feature generic\_const\_expressions. I would really appreciate if you have a knowledge on how to make it "just using unsafe". _Especially for unnamable types, like futures - not just store Foo\<'static\> and unsafely write Foo\<'a\>, because you cannot rewrite lifetimes of unnamable type - maximum it just get it with TAIT feature_

---

_[View the full topic](https://internals.rust-lang.org/t/non-static-data-in-static/21247)._