InKryption

Was no issue, by the way. The small effort that it was amounted to just undoing your TODO on the enum, which ends up being fixed in this version of...

> Shouldn't you know what type you are expecting to find? In that case, why don't we just abandon the `anytype` here, and require a specific type? ``` pub fn...

Thank you for the links. I'll note here that although I've left a good few of the ENABLE_GUARDs in tact, I did explicitly decide to omit a few, namely: *...

I didn't realize this was an open issue. I think this should be closed; I like the fact that declarations have to be written out by the programmer, it makes...

It sounds like this proposal as written would make https://github.com/SuperAuguste/cursed-zig-errors no longer work, which seems like a positive change (and probably a necessary one for its existence to not pose...

Isn't the `extern` part of this actually irrelevant? We can't do this with normal `var`s either: 

I would suggest a design that allows you to specify the encode/decode behavior at the call-site, i.e. out-of-band codecs. There's a lot of ways to design that, some more complex...

I think the question of whether to populate `argv` on Windows could go either way; you can always opt-out of any `argv` population by exporting the entry point directly. Or...

I think, put like that, I would be in favor of the third option: `std.os.argv` should be removed.

Just a note to keep in mind when working on this: often a useful pattern for creating helpful error traces is to make return types be `noreturn` if the parameters...