# Memory corruption in slice initialization (probably)

**URL:** <https://ziggit.dev/t/memory-corruption-in-slice-initialization-probably/6333>\
**Category:** Help\
**Tags:** language\
**Created:** [October 11, 2024, 6:13am UTC](https://ziggit.dev/t/memory-corruption-in-slice-initialization-probably/6333 "2024-10-11T06:13:28Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tensorush](https://ziggit.dev/letter_avatar_proxy/v4/letter/t/6a8cbe/32.png) [@tensorush](https://ziggit.dev/u/tensorush)\
**Post date:** [October 11, 2024, 7:07am UTC](https://ziggit.dev/t/memory-corruption-in-slice-initialization-probably/6333/3 "2024-10-11T07:07:18Z")

</div>

Also, the reason it didn’t work in your case is because `fields` is a local function variable, so you _can’t_ return a pointer to it. However, it worked in the commented-out case because that [tuple](https://ziglang.org/documentation/0.13.0/#Tuples) has a static lifetime since it only contains comptime-known data, so you _can_ return a pointer to it (see [Diving deep into anonymous struct literals](https://ziggit.dev/t/diving-deep-into-anonymous-struct-literals/2931)).

---

_[View the full topic](https://ziggit.dev/t/memory-corruption-in-slice-initialization-probably/6333)._
