Rohlem

As far as I understand, the wiki page links to "wishlists" of what would be valuable for the Zig toolchain to prioritize for the benefit of other projects. Other entries...

> It also can turn temporary bugs from crashers into "this part didn't render", which is a clear win for robustness. My only concern with this strategy would be that...

For bit operations that are sensible for a particular type, you can already declare methods on the type. For your second initial point, for common combinations you may consider [decl...

> If I write `foo()` at runtime, that is a 3-phase process: > > * Get the pointer value `&foo` > > * Dereference that pointer > > * Call...

> Specifically, given `expr()`, how do we lower `expr` to ZIR? If we lower it as an rvalue, then there _will_ be a pointer load instruction. I don't know why...

> The expression `&foo` is a pointer; if you had to call extern functions as `(&foo)()`, then everything would be fine. But that's ridiculous to require. I still don't know...

> `@subWithOverflow` [...] would work cleanly with returning an `i1` instead of a `u1`: A carry returns `-1` and no carry returns `0`. In this case carries can be naively...

@mhcerri Error unions use error values, which under-the-hood are a program-wide enum (to allow easier coercion from any smaller error set to the global error set `anyerror`). So every time...

> > Slightly related: over 80 percent of the 200MB `zig1.c` file consists of indenting white spaces, I think it's worth trimming down a bit. > > It's nice to...

First off, the solution with the smallest-footprint change could look like this: ```zig @comptimeRealloc(old_mem: []u8, new_size: usize, new_align: u29) ?[]u8 //returns null if evaluated at runtime ``` --- For a...