David Rubin

Stack Trace ``` /home/dr/zig/lib/std/debug.zig:403:14: 0x8004b53 in assert () if (!ok) unreachable; // assertion failure ^ /home/dr/zig/src/Sema.zig:1904:11: 0x8ed6e2f in resolveType () assert(air_inst != .var_args_param_type); ^ /home/dr/zig/src/Sema.zig:4648:32: 0x94b33e9 in zirValidateArrayInitTy () const...

This is incorrect; the function parameter is slice, which is a pointer. Please read [the langref a bit more](https://ziglang.org/documentation/master/#Pointers).

This error occurs while building the zap dependency. If you read their README you will see this: >Q: Does ZAP work on Windows? A: No. This is due to the...

The error message is very clear. This isn't a problem with the compiler or the library. Zap simply does not support Windows, and so doesn't use the cross-platform version of...

I see what you mean. I agree it's a bit annoying that it doesn't explicitly say what dependency threw the error. How I figured it out was by seeing `zig\p\{hash}\build.zig`...

here's the smallest repro I was able to do: ```zig pub const Foo = packed struct(u32) { a: u16 = undefined, b: packed struct(u16) { c: u6 = 0, d:...

> note that `@clampTo` can already be estimated with `@max`. for example `@max(unsigned_int, 255)` will always yield a `u8`. This is simply not true. `@max` will yield the larger type...

this is a good PR and all, but some of the strategies ive used aren't really clean and i dont like them. ill make this a draft while i redo...

it really shouldn't have been that difficult to merge in a couple more commits 😄 anyways, i've rewritten a large part of the pointer management, i'm happy enough for this...

marked as draft because these points are still left before this can land / be reviewed: - [x] Rewrite stack frame abstraction. - [x] Finish simplified test runner and get...