Stevie Hryciw

Great, looking forward to having this! Thanks for having `addModule()` return the module as well. From the compiler meeting this week, it sounds like Module should have `installHeader()` and friends...

It looks like the traces are short when the function signature itself causes a compile error. Each of these examples cause a compile error whose error trace doesn't lead all...

Oh. Aside from the "unclear error message" aspect, the stack trace issue is the same as #12969. Also possibly related to #1295.

I see potential in that. A world where error sets are just regular unions, but given all the syntax-level amenities of today's errors. ```zig // a regular-ass type const InvalidChar...

Rebased on master and cleaned up. I'll keep this in a perpetual review-ready state from this point. If you want to refer to any of the earlier commits that are...

@rohlem I've contemplated that "define/instantiate a function of named type `F`" idea before, but it breaks down quickly for a few reasons: 1. The parameter names are not part of...

That's insightful, thank you. I wasn't sure if the idea was valid, and sounds like it might not be the right tool for the job (though I'm still looking forward...

I'm also getting this on Arch Linux with systemd-networkd and systemd-resolved. Working just fine on macOS though. Not sure if this helps but: ``` $ strace --trace=network zig build test...

I see a different error now, `error.ConnectionFailed`. The strace output looks identical to before. Let me know if there are any better diagnostics I can provide.

I went to debug this by altering std.http.Client, but got a strange result before I even changed any code. I checked out 602029bb2 (commit of latest release at the time...