# Init block to const-cast - does it copy?

**URL:** <https://ziggit.dev/t/init-block-to-const-cast-does-it-copy/14563>\
**Category:** Help\
**Tags:** language\
**Created:** [March 9, 2026, 3:13pm UTC](https://ziggit.dev/t/init-block-to-const-cast-does-it-copy/14563 "2026-03-09T15:13:24Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![mnemnion](https://ziggit.dev/user_avatar/ziggit.dev/mnemnion/32/2478_2.png) [@mnemnion](https://ziggit.dev/u/mnemnion)\
**Post date:** [March 9, 2026, 9:30pm UTC](https://ziggit.dev/t/init-block-to-const-cast-does-it-copy/14563/11 "2026-03-09T21:30:43Z")

</div>

> [@Justus2308](#):
>
> The current behavior is considered a bug and _will_ (likely) break sometime in the future.

This isn’t tagged with either bug, or accepted, it’s just an issue. There’s substantial debate within that thread about what the problem actually is, I think your confidence is unjustified.

Andrew also tagged it ‘unplanned’ so, there’s that.

> [@jumpnbrownweasel](#):
>
> I think @mnemnion is hoping that never happens.

Yes I think it would be foolish to tie lifetimes to block scope in addition to function scope. There was [a long thread about this](https://ziggit.dev/t/what-makes-ban-returning-pointer-to-stack-memory-difficult/9380) awhile back, my position is that better liveness analysis solves the excessive stack use, and with that solved, all that block-scoping lifetimes would accomplish is breaking obviously-useful code like that shown above.

---

_[View the full topic](https://ziggit.dev/t/init-block-to-const-cast-does-it-copy/14563)._