Meghan Denny
Meghan Denny
should there be a `.hot` ?
as an opposite to aforementioned `.cold`. `/// This branch of control flow is likely to *always* be reached.`
imo `Reader.readStruct` shouldn't be in the stdlib. there's too many variables wrt to padding and endianness that it should be left to the user
x86_64-windows still uses the llvm backend by default at the time of writing so that comparison isn't representative
I think whats happening is that `list.items` in main is a stale pointer because `addToList` causes the backing allocation to be reallocated in order to grow in size
more specifically: - `list.items` in main is `&.{}` - `addToList` causes it to be `allocator.alloc(1)` since `list.capacity` is `0` - `list.items.len` is now `1` but the temporary had already been...
its exhibiting the same failure as ```zig pub fn main() !void { const x = list.items; // { ptr: undefined, len: 0 } is on the stack const y =...
i think tracking issues such as this usually stay open until the llvm 19 upgrade is completed
> This proposal is for `zig build` to additionally copy each dependency from the global cache into a project-local directory, like this: > > ``` > $PROJECT_ROOT/zig-deps/$DEPENDENCY_NAME/* > ``` >...
`zig build --fetch` will already do that, and is orthogonal to this feature request edit: the issue was also that they were doing a http request in their configure phase