aboutsummaryrefslogtreecommitdiff
path: root/lib/libc/include/arc-linux-gnu/bits
diff options
context:
space:
mode:
authormlugg <mlugg@mlugg.co.uk>2025-01-29 06:39:29 +0000
committerMatthew Lugg <mlugg@mlugg.co.uk>2025-01-29 18:43:24 +0000
commit107b65ec5dccd360410b4a693bb0caf0015312f3 (patch)
tree7cd66974406b4f3423e746f1ca24c0e7f0cabb94 /lib/libc/include/arc-linux-gnu/bits
parent484f72311eae288ed5c7a648ec016b02f4547f48 (diff)
downloadzig-107b65ec5dccd360410b4a693bb0caf0015312f3.tar.gz
zig-107b65ec5dccd360410b4a693bb0caf0015312f3.zip
Sema: explain why we tried to call an `extern fn` at comptime
I recently saw a user hit the "comptime call of extern function" error, and get confused because they didn't know why the scope was `comptime`. So, use `explainWhyBlockIsComptime` on this and related errors to add all the relevant notes. The added test case shows the motivating situation.
Diffstat (limited to 'lib/libc/include/arc-linux-gnu/bits')
0 files changed, 0 insertions, 0 deletions