- 28 story files gain YAML frontmatter: iteration id, status (mirrors folder), chain position (7 files, positions 1-6) - board-views.md: Dataview queries (not-done, by-status lanes, chain order, active); Kanban caveat — view only, frontmatter is source of truth, folder move + status key change together - board points at the views Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
3.1 KiB
| iteration | status |
|---|---|
| 5 | done |
Iteration 5 — language surface (Haxe-parity adoptions)
Format:
product/story-iteration-template. Part of Story — one language, one runtime, one database, one binary.
Status: ✅ COMPLETE 2026-08-20. The grammar half landed 2026-08-14 — modules,
and/or, interpolation,const, loop control, switch expressions, typedef records, enum payloads, try/catch,nil/?T, statics,pub(read)syntax, container literals,for k, v in m,as. The strictness half landed in three waves:?Tforced handling (WO-E211/212/213 + narrowing) and reject rows (WO-E105) on 2026-08-18; the final three on 2026-08-20 (branchlanguage-surface-strictness, developer directive overriding the post-12 park) —pub(read)write enforcement (WO-E219, class-owned writes, corpus-pinned),usingstatic extensions (compile-time rewrite to a free-fn call, WO-E220 on method collision, zero owner/emit awareness), and#ifbuild flags (woc -D name, token-level filter, WO-E003 misuse).is/throwstay cut (0 workload uses);abstractis a reject row. Plan 8 is closed.
Goals
- The language grows from milestone grammar to a daily-driver surface: the
systems-track verdict table's every adopt row — switch expressions,
typedef records with
?fields,?Toptionals with null-narrowing, enum payload variants, try/catch/throw over traps,staticmembers,abstractnewtypes,usingextensions,usemodules,is,pub/pub(read),#ifbuild flags, string interpolation, loop control. - Every reject row (inheritance,
Dynamic,cast, macros, FFI…) refuses with a diagnostic citing doctrine — the language's boundaries are as deliberate as its features.
Acceptance Criteria
- What to achieve?
- Given the verdict table in the systems-track spec,
- when the corpus runs,
- then every adopt row has at least one golden fixture and one must-fail fixture passing, and every reject row that would parse produces its doctrine-citing diagnostic.
- What to achieve?
- Given a switch over a union missing one variant and lacking
default, - when it compiles,
- then the diagnostic names exactly the missing variants.
- Given a switch over a union missing one variant and lacking
- What to achieve?
- Given the three fenced VM changes (catch frames, variant objects, boxed scalar optionals),
- when they land,
- then the format doc is updated in the same change and all prior trap fixtures still pass byte-for-byte.
Out Of Scope
- Stdlib modules and program mode (iteration 6).
- Any new VM capability beyond the three fenced changes.
Info
- Normative table:
docs/superpowers/specs/2026-08-01-systems-track-design.mdPart 1. - Order inside the plan matters: modules first (everything imports through them), data shapes before optionals, rejects last.
Proposed Solution
- Execute the existing plan:
compiler/plan/2026-08-01-haxe-parity-language.md(nine tasks, each shipping its fixtures and error-catalog entries in the same task).