# Writing runtime-extensible code in Zig is massively inconvenient

**URL:** <https://ziggit.dev/t/writing-runtime-extensible-code-in-zig-is-massively-inconvenient/10036>\
**Category:** Brainstorming\
**Tags:** language\
**Created:** [May 8, 2025, 5:51pm UTC](https://ziggit.dev/t/writing-runtime-extensible-code-in-zig-is-massively-inconvenient/10036 "2025-05-08T17:51:14Z")\
**Posts on this page:** 1\
**Showing post:** 20

<div class="post-metadata">

**Author:** ![cancername](https://ziggit.dev/user_avatar/ziggit.dev/cancername/32/8752_2.png) [@cancername](https://ziggit.dev/u/cancername)\
**Post date:** [May 9, 2025, 12:21am UTC](https://ziggit.dev/t/writing-runtime-extensible-code-in-zig-is-massively-inconvenient/10036/20 "2025-05-09T00:21:08Z")

</div>

> [@cancername](#):
>
> maybe a `@abiLayout(.foobar_layout, T)` builtin or something similar to guarantee a layout for that type would be a language-level solution?

Coincidentally, this would also make [saving space by omitting the safety-checking tag](https://ziggit.dev/t/can-i-disable-the-safety-checking-tag-on-a-bare-union-without-packed/4605/2) possible without that cursed hack, assuming there are `safe` and `unsafe` ABIs: `@AbiLayout(.unsafe, union{...})`.

---

_[View the full topic](https://ziggit.dev/t/writing-runtime-extensible-code-in-zig-is-massively-inconvenient/10036)._
