Motiejus Jakštys
aff6dd419c
- retExpr: check nodesNeedRl to use RL_PTR with ret_ptr/ret_load instead of always RL_COERCED_TY with ret_node. Handle .always/.maybe error paths with load from ptr when needed. - Use typeExpr() instead of expr()/exprRl() for type sub-expressions in optional_type, error_union, merge_error_sets, and array elem types in structInitExpr/arrayInitExpr. This generates BLOCK_COMPTIME wrappers for non-primitive type identifiers. - arrayInitExpr: only use ARRAY_INIT_REF for RL_REF (not RL_REF_COERCED_TY), and pass non-ref results through rvalue(). - slice_sentinel: emit SLICE_SENTINEL_TY and coerce sentinel to that type. All slice variants: coerce start/end to usize. - COERCE_PTR_ELEM_TY in rvalue for RL_REF_COERCED_TY. - rvalueNoCoercePreRef for local variable references. - structInitExprPtr/arrayInitExprPtr for RL_PTR with OPT_EU_BASE_PTR_INIT. - Typed struct init: use RL_COERCED_TY with field type for init expressions. Reduces parser_test.zig corpus diff from 225 to 5 instructions. 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.