-
-
Notifications
You must be signed in to change notification settings - Fork 0
Codegen: implement target emission and document the pipeline #40
Copy link
Copy link
Open
Labels
architectureStructural/system-level shape and runtime behaviourStructural/system-level shape and runtime behaviourenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourpriority:p2Normal - queue itNormal - queue itscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
Description
Activity
Metadata
Metadata
Assignees
Labels
architectureStructural/system-level shape and runtime behaviourStructural/system-level shape and runtime behaviourenhancementNew capability or improvement to existing behaviourNew capability or improvement to existing behaviourpriority:p2Normal - queue itNormal - queue itscope:repoConfined to this repositoryConfined to this repositorystatus:readyFully specified and ready to be picked upFully specified and ready to be picked up
Problem
src/codegen/*(consent.rs,accessibility.rs,i18n.rs,parser.rs) are stubs — thegeneratepipeline does not yet emit target-language code end-to-end. The README/decorator reference implies a working pipeline, which slightly over-claims current capability.Scope
@consent,@accessible,@i18ndecorators.manifest -> validate -> generateend-to-end with a real example underexamples/compliant-app/.docs/developer/CODEGEN.adocdocumenting the stages (parse → ABI validation → emit) and extension points (how to add a decorator).Context
The ABI (Idris2) and FFI (Zig) layers are real and tested; codegen is the missing piece for the MVP (see
.machine_readable/6a2/STATE.a2mlroute-to-mvp).