# Should I bother with deinit()?

**URL:** <https://ziggit.dev/t/should-i-bother-with-deinit/12878>\
**Category:** Help\
**Tags:** memory-management\
**Created:** [November 6, 2025, 3:49pm UTC](https://ziggit.dev/t/should-i-bother-with-deinit/12878 "2025-11-06T15:49:50Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![g41797](https://ziggit.dev/user_avatar/ziggit.dev/g41797/32/3339_2.png) [@g41797](https://ziggit.dev/u/g41797)\
**Post date:** [November 7, 2025, 3:13pm UTC](https://ziggit.dev/t/should-i-bother-with-deinit/12878/10 "2025-11-07T15:13:45Z")

</div>

> [@pachde](#):
>
> In a library, probably best to let the library user decide allocation policy

**Just clarification** - I agree with _probably best_ because it does not mean _always_

If _allocation policy_ means allocator, It depends on library

It’s OK for zig std library or similar style where code is visible , but for library with own internal multithreading,  
I’d like to force(ask) user to give “me” malloc compatable allocator  
we already had [long discussion](https://ziggit.dev/t/allocators-and-thread-safety-and-not-only)

---

_[View the full topic](https://ziggit.dev/t/should-i-bother-with-deinit/12878)._