Rohlem
Rohlem
I think I can see arguments for both evaluation orders: Reading `list.items` before it was updated is left-to-right reading order, reading it after it was updated might conserve stack space....
typo in the issue name (`anytime` -> `anytype`)
IIUC, updating procedure would always be to uninstall the old version first, since the set of installed files might change due to the update. I'm not sure if this is...
It's already noted in the issue text, but important to note that coercion of pointers-to-const `*const *align(2) T` -> `*const *align(1) T` can be allowed. We only need to prevent...
> * They allow constructing error values at comptime with `@field` (for instance, `@field(anyerror, my_string)`). This isn't used in practice, but could hugely harm readability of a codebase if it...
> you should definitely _not_ be constructing error names based on comptime-known strings. This screams of a poorly-designed API. I don't use `@field(anyerror, x)` as the primary source of any...
@mlugg Thanks for your response. > the example given in that proposal is taking the wrong approach: rather than trying to make the language support error sets varying based on...
> I'm unsure if this is an issue that needs fixing. The issue is https://github.com/ziglang/zig/issues/21655 , where correct code for a generic data structure in status-quo would need special-casing. Discussion...
I don't know much about Linux; maybe I'm spouting nonsense, but couldn't the opposite, hypothetically, be true as well? If a syscall is "upgraded" to loosen its preconditions, then what...
I see an open issue https://codeberg.org/ziglings/exercises/issues/127 and PR https://codeberg.org/ziglings/exercises/pulls/130 about recent build errors in their repository. It's unclear whether you are double-reporting the same thing here, or something completely different....