David Rubin

Almost certainly an effect of 58d2bd601e3b25e818d6bca2b3267052a12f9917 cc @jacobly0

Better reduction: ```zig const Empty = struct {}; comptime { const X = @sizeOf(Empty); @compileLog(X); switch (X) { 0 => {}, else => @compileError("here"), } } ``` ``` empty.zig:8:17: error:...

The core bug has been around for much longer, it seems. I can reproduce the issue on 0.13.0.

I see no purpose in providing a "defined here" note. The error message is focused on the fact that you cannot compare `u32` to an enum. *Which* enum is at...

> should there be a `.hot` ? Just saying `.hot` doesn't provide the context of what it would do. Can you explain how it would affect code generation?

> as an opposite to aforementioned `.cold`. `/// This branch of control flow is likely to *always* be reached.` You have described `.likely`. How would `.hot` be different from `.likely`?...

> No upgrade path was provided. `@setCold(true)` -> `@branchHint(.cold)`. > Can these builtins even be effectively conditionally compiled? It is far from clear. No, `@setCold` has been fully removed. >...

Moving my suggestion from the Discord, I thought it'd be cool if the sound was generated as a normalization of the bytes that were used to find the bug 😄...

Can confirm. It's this line right here: https://github.com/ziglang/www.ziglang.org/blob/72cbd7c2d19f5f0b2b5cbfdeb9f288b5b2df9392/src/documentation/0.13.0/index.html#L319 where I guess it's supposed to be using something like this here: https://github.com/ziglang/www.ziglang.org/blob/72cbd7c2d19f5f0b2b5cbfdeb9f288b5b2df9392/src/documentation/0.12.0/index.html#L306C19-L306C25

Zig repro: ```zig test { var v: @Vector(4, u80) = .{ 10, 20, 30, 40 }; var x: @Vector(4, u80) = .{ 1, 2, 3, 4 }; _ = .{...