Repository navigation
[TASK-012] Multi-file gen: resolve use/import across specs for coherent output #64
Description
Activity
🚀 Starting work on
t27c compile-projectcommand.Branch:
feat/compile-project
Plan:- Explore existing compile infrastructure
- Implement module → path mapping
- Generate coherent project structure with resolved imports
- Generate build.zig
- Test end-to-end
- PR targeting master
- added a commit that references this issue
on Apr 4, 2026 Completed — PR #68 merged.
What was added
t27c compile-project --output <dir> [--backend zig|c|verilog]Three-pass compilation:
- Scan — builds module→path map from all .t27 files
- Resolve — converts
use X::Yto correct relative@importpaths - Write — outputs structured project +
build.zig
Results
- 43 files compiled, 0 errors
- Cross-namespace imports resolved (e.g.
use base::typesinar/asp_solver.t27→@import("../base/types.zig")) - Same-namespace imports stay local (e.g.
@import("ternary_logic.zig")) build.zigdeclares all 43 modules as a static library
Output structure
build/ ar/asp_solver.zig, composition.zig, ... base/types.zig, ops.zig math/constants.zig, sacred_physics.zig numeric/gf16.zig, gf4.zig, ... nn/hslm.zig, attention.zig ... build.zig- added a commit that references this issue
on Jun 1, 2026
Cross-file import resolution
Currently each spec generates independently. For real compilation:
use base::typesshould resolve to the types moduleAdd
t27c compile-project --output build/that generates ALL specs into a coherent project structure with working imports.phi^2 + 1/phi^2 = 3 | TRINITY