Andrew Kelley 3c2a43fdcc Revert "std: check types of pointers passed to allocator functions" ... This reverts commit abc9530a88. This patch implies that the idiomatic Zig way of handling anytype parameter is to write a bunch of boilerplate instead of directly accessing type information and relying on the compiler to be useful. I don't want it to be this way. It is the compiler's job to make useful error messages when the wrong field of a type info result is accessed, and it is the zig programmer's job to understand what it means when a compile error points at the field access of `@typeInfo` (along with the relevant callsites). One thing that might be useful would be having the compiler be aware of module boundaries and highlighting the boundaries of them. The first reference note after crossing a module boundary is likely the most interesting one.		2023-02-12 05:59:28 -07:00
..
arena_allocator.zig	Implements std.ArenaAllocator.reset() (#12590)	2023-01-03 15:15:20 -05:00
general_purpose_allocator.zig	Revert "std: check types of pointers passed to allocator functions"	2023-02-12 05:59:28 -07:00
log_to_writer_allocator.zig	std.mem.Allocator: allow shrink to fail	2022-11-29 23:30:38 -07:00
logging_allocator.zig	std.mem.Allocator: allow shrink to fail	2022-11-29 23:30:38 -07:00
memory_pool.zig	Improves the comment formatting.	2022-12-15 10:16:28 +01:00
PageAllocator.zig	std.heap: extract PageAllocator, WasmPageAllocator	2022-11-29 23:46:02 -07:00
WasmAllocator.zig	WasmAllocator: simplify thanks to new Allocator interface	2022-11-29 23:46:02 -07:00
WasmPageAllocator.zig	std.heap.WasmAllocator: redo	2022-11-29 23:46:02 -07:00