Kaylee Blake

Yeah, the toBoolean\1 was the only one I was sure about.

This replicates the issue directly on `std.heap.page_allocator`: ```zig const std = @import("std"); const page_allocator = std.heap.page_allocator; var pages: [128 * 1024]*[4096]u8 = undefined; pub fn main() !void { for (&pages)...

It's worth noting that `madvise(MADV_DONTNEED_LOCKED)` will discard the underlying memory backing the region passed to it, without affecting the VMA, and so will succeed as long as arguments are aligned...

I'd be surprised if you could 64 bit address space exhaustion from this naturally, I'd expect you'd only really see it in programs deliberately trying to trigger it. For 32...