Track generated files and run-artifact outputs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Problem
Generated-source workflows are central to large Zig projects. Azazel has pre commands, but replacement parity needs generated output tracking.
Needed
- Model run artifacts that produce files.
- Attach generated outputs to module source/import/include paths.
- Support generated version files, protocol translations, manpage generation, and table generation.
- Make output paths explicit in generated
build_spec.zig.
Corpus drivers
- ZLS generated version data.
- River generated protocol modules.
- libxev generated pkg-config/manpage-style outputs.
- libvaxis generated Unicode tables through
uucode_generate.
Done when
- A generated file can be declared in
project.cue, produced before compile, and consumed by a module. tools/huge_corpus.py --parity --repo libvaxiscan validate a generated-output target slice.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with project.cue and the generated build_spec.zig output, then inspect tools/huge_corpus.py --parity --repo libvaxis. Compare the generated-output cases described for ZLS, River, libxev, and libvaxis. Done means a generated file can be declared, produced before compilation, consumed by a module, and validated by the target parity slice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100