compiler-internals

The Kukicha compiler pipeline processes .kuki source files sequentially through the lexer, parser, AST, semantic analysis, IR, and codegen stages to generate final Go code. Each stage passes specific data structures to the next.

To debug compiler bugs in semantic analysis or IR stages, review the internal/ package documentation to understand module responsibilities and data flow, then run the compiler tests to validate and isolate your internal changes.

Yes, you can extend the Kukicha compiler by adding new language features to the AST. Use the component map to identify module responsibilities and reason about how changes across the parser and codegen interact.

Known fragility risks when modifying Kukicha compiler internal packages involve integration points between the lexer, parser, and codegen. Reviewing the component map helps identify these risks and validate changes against error handling and security checks.

Yes, you need Go installed because the Kukicha compiler's codegen stage outputs generated Go code. Reviewing the internal package documentation and running compiler tests requires the Go environment to validate modifications.

The Kukicha compiler includes LSP and diagnostics integration to provide real-time error handling and feedback during development. This architecture helps developers identify issues across the lexer, parser, and semantic analysis stages efficiently.