Motiejus
285935bd41
Add builtins: @sizeOf, @alignOf, @typeInfo (simpleUnOpType pattern), @compileError, @setEvalBranchQuota, @typeName (simpleUnOp pattern), @This (addNodeExtended), @memmove, @FieldType, @reduce, @addWithOverflow/@subWithOverflow/@mulWithOverflow/@shlWithOverflow (overflowArithmetic), @alignCast/@constCast/@volatileCast (ptrCast family), @errSetCast, @Type (reify), @TypeOf (typeof_builtin block), @unionInit (3-arg via builtinCallMultiArg), @intFromPtr, @intFromBool, @floatFromInt, @intFromFloat, @floatCast. Add helper functions: addNodeExtended, addExtendedPayload, addExtendedPayloadSmall. Add is_typeof field to GenZir. Add AST_NODE_BUILTIN_CALL dispatch for 3+ arg builtins. Add COMPTIME_REASON_COMPILE_ERROR_STRING and UNION_FIELD_NAME. Add skipped corpus tests for array_list.zig, multi_array_list.zig, Sema.zig (blocked on identifier resolution across namespace scopes). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
About
zig0 aspires to be an interpreter of zig 0.15.2 written in C.
This is written with help from LLM:
- Lexer:
- Datastructures 100% human.
- Helper functions 100% human.
- Lexing functions 50/50 human/bot.
- Parser:
- Datastructures 100% human.
- Helper functions 50/50.
- Parser functions 5/95 human/bot.
- AstGen: TBD.
Testing
Quick test:
zig build fmt-zig0 test-zig0
Full test and static analysis with all supported compilers and valgrind (run before commit, takes a while):
zig build all-zig0 -Dvalgrind
Debugging tips
Test runs infinitely? Build the test program executable:
$ zig build test-zig0 -Dzig0-no-exec
And then run it, capturing the stack trace:
gdb -batch \
-ex "python import threading; threading.Timer(1.0, lambda: gdb.post_event(lambda: gdb.execute('interrupt'))).start()" \
-ex run \
-ex "bt full" \
-ex quit \
zig-out/bin/test
You are welcome to replace -ex "bt full" with anything other of interest.