Compiler Architecture Best Practices
9 sections
0%
Section 1 Foundation & Policy Rules Section 2 AST/IR Immutability Contract Section 3 Type Solver Budget Infrastructure Section 4 Diagnostic Ordering & Suppression Section 5 Incremental Edit-Sequence Testing Section 6 Cross-Target Codegen Verification Section 7 TypeFolder Trait Section 8 Packed Symbol Representation Section 9 Layout Caching via Salsa Query
Overview
Implement verified industry best practices and documented aspirational patterns as enforceable rules with supporting infrastructure, creating the foundational correctness-enforcement layer that ALL downstream plans build on. This plan closes 6 confirmed gaps surfaced by a dual-source (Codex + Gemini) TPR review against 10 reference compilers (Rust, Go, TypeScript, Zig, Swift, Gleam, Roc, Elm, Koka, Lean 4), plus 3 aspirational patterns already documented in impl-hygiene.md §Aspirational Patterns. Effort is not a constraint — this is about building the best possible architectural foundation.
Planned
9 sections
Section 1 Not Started
Foundation & Policy Rules
0/18 tasks
0/18 tasks
Section 2 Not Started
AST/IR Immutability Contract
0/11 tasks
0/11 tasks
Section 3 Not Started
Type Solver Budget Infrastructure
0/28 tasks
0/28 tasks
Section 4 Not Started
Diagnostic Ordering & Suppression
0/23 tasks
0/23 tasks
Section 5 Not Started
Incremental Edit-Sequence Testing
0/19 tasks
0/19 tasks
Section 6 Not Started
Cross-Target Codegen Verification
0/18 tasks
0/18 tasks
Section 7 Not Started
TypeFolder Trait
0/30 tasks
0/30 tasks
Section 8 Not Started
Packed Symbol Representation
0/32 tasks
0/32 tasks
Section 9 Not Started
Layout Caching via Salsa Query
0/30 tasks
0/30 tasks