Motiejus Jakštys
0df3e81e6a
Mechanically match upstream comptimeExpr signature which accepts ResultInfo. This fixes coercion in comptime contexts (e.g. sentinel 0 becoming zero_u8 instead of generic zero when elem_type is u8). - comptimeExpr: add ResultLoc rl parameter, thread to exprRl - typeExpr: pass coerced_ty=type_type (matching upstream coerced_type_ri) - ptrType: pass ty=elem_type for sentinel, coerced_ty=u29 for align, coerced_ty=u16 for bit_range - retExpr: set RI_CTX_RETURN - tryExpr: set RI_CTX_ERROR_HANDLING_EXPR for operand - orelseCatchExpr: set RI_CTX_ERROR_HANDLING_EXPR when do_err_trace - ifExpr: set RI_CTX_ERROR_HANDLING_EXPR for error union condition - shiftOp: set RI_CTX_SHIFT_OP, use as_shift_operand in rvalue - breakResultInfo: don't forward ctx for discard case - fnDecl ret_body break: use AST_NODE_OFFSET_NONE Passes corpus tests for test_all.zig, build.zig, tokenizer_test.zig. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
About
zig0 aspires to be an interpreter of zig 0.15.1 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 test
Full test and static analysis with all supported compilers and valgrind (run before commit, takes a while):
zig build -Dvalgrind
Debugging tips
Test runs infinitely? Build the test program executable:
$ zig build test -Dno-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.