aboutsummaryrefslogtreecommitdiff
path: root/lib/std/Build/CompileStep.zig
diff options
context:
space:
mode:
authorAndrew Kelley <andrew@ziglang.org>2023-02-12 05:59:28 -0700
committerAndrew Kelley <andrew@ziglang.org>2023-02-12 05:59:28 -0700
commit3c2a43fdcc2d9aeafafe7ef37c7b805e18fac351 (patch)
tree99050b8c99b38756448f321c145b926d0efff95c /lib/std/Build/CompileStep.zig
parentabc9530a88d24350481d9264edcde300f293929a (diff)
downloadzig-3c2a43fdcc2d9aeafafe7ef37c7b805e18fac351.tar.gz
zig-3c2a43fdcc2d9aeafafe7ef37c7b805e18fac351.zip
Revert "std: check types of pointers passed to allocator functions"
This reverts commit abc9530a88d24350481d9264edcde300f293929a. 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.
Diffstat (limited to 'lib/std/Build/CompileStep.zig')
0 files changed, 0 insertions, 0 deletions