Meghan Denny

text of trace above ``` error: thread 5468577 panic: reached unreachable code /Users/dk/src/zig/zig/src/link/Dwarf.zig:2930:33: 0x1091e371b in updateComptimeNav (zig) /Users/dk/src/zig/zig/src/link/Elf/ZigObject.zig:1617:64: 0x1091c70a3 in updateNav (zig) /Users/dk/src/zig/zig/src/link/Elf.zig:2723:43: 0x108f6322f in updateNav (zig) /Users/dk/src/zig/zig/src/link.zig:650:81: 0x108d19183 in...

example of a repo that does it today (with afl integration) (with separate `zig build test` and `zig build fuzz` steps) https://github.com/nektro/zig-json

> `@Type(.Null)` is equivalent to `@TypeOf(null)` and it is unclear which is preferred, and that is a problem. both should be avoided in favor of proper optionals. `@Type(.Null)` should be...

> If we did do this, we could very well make helper functions in `std.meta`, in the case of pointers, floats and arrays. given how simple their construction, i think...

@Apppppppple `@Type` could easily be reimplemented in `std.meta` after this change

> This file is itself a binary file I like this idea but think ^ would be a critical mistake. also this seems very similar to https://en.wikipedia.org/wiki/Interface_description_language

no, open the pr directly and reference back to this. include the test program you got to pass and command you ran to test in the pr description

in my experience this is fixed by adding `-lc` to your `zig build-obj` calls

notes: i get this with the no-package example on arm64 macos ``` ❯ node index.js { error: 'File type not allowed', code: 801 } ``` ``` ❯ bun index.js {...

https://www.youtube.com/watch?v=jy7w_7JZYyw https://github.com/ziglang/zig/blob/master/doc/build.zig.zon.md