tomoaki
757193891f
## Summary Implemented fail-fast validation for PHI ordering and value resolution in strict mode. ## Changes ### P1-1: Strict mode for "PHI after terminator" - File: `src/llvm_py/phi_wiring/wiring.py::ensure_phi` - Behavior: `NYASH_LLVM_PHI_STRICT=1` → RuntimeError if PHI created after terminator - Default: Warning only (no regression) ### P1-2: Strict mode for "fallback 0" - File: `src/llvm_py/phi_wiring/wiring.py::wire_incomings` - Behavior: Strict mode forbids silent fallback to 0 (2 locations) - Location 1: Unresolvable incoming value - Location 2: Type coercion failure - Error messages point to next debug file: `llvm_builder.py::_value_at_end_i64` ### P1-3: Connect verify_phi_ordering() to execution path - File: `src/llvm_py/builders/function_lower.py` - Behavior: Verify PHI ordering after all instructions emitted - Debug mode: Shows "✅ All N blocks have correct PHI ordering" - Strict mode: Raises RuntimeError with block list if violations found ## Testing ✅ Test 1: strict=OFF - passes without errors ✅ Test 2: strict=ON - passes without errors (no violations in test fixtures) ✅ Test 3: debug mode - verify_phi_ordering() connected and running ## Scope - LLVM harness (Python) changes only - No new environment variables (uses existing 3 from Phase 277 P2) - No JoinIR/Rust changes (root fix is Phase 279) - Default behavior unchanged (strict mode opt-in) ## Next Steps - Phase 278: Remove deprecated env var support - Phase 279: Root fix - unify "2本のコンパイラ" pipelines 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
40 lines
2.3 KiB
Markdown
40 lines
2.3 KiB
Markdown
# Nyash Language Reference – Index
|
||
|
||
This is the entry point for Nyash language documentation.
|
||
|
||
- Full Language Reference (2025): reference/language/LANGUAGE_REFERENCE_2025.md
|
||
- Syntax Cheat Sheet: quick-reference/syntax-cheatsheet.md
|
||
- Phase 12.7 Grammar Specs (ternary, sugar; peek → match に統合):
|
||
- Overview: development/roadmap/phases/phase-12.7/grammar-specs/README.md
|
||
- Token/Grammar: development/roadmap/phases/phase-12.7/ancp-specs/ANCP-Token-Specification-v1.md
|
||
- Sugar Transformations (?., ??, |> and friends): parser/sugar.rs (source) and tools/nyfmt/NYFMT_POC_ROADMAP.md
|
||
- Match Expression (pattern matching): see the Language Reference and EBNF (peek was replaced by match)
|
||
|
||
Statement separation and semicolons
|
||
- See: reference/language/statements.md — newline as primary separator; semicolons optional for multiple statements on one line; minimal ASI rules.
|
||
|
||
Imports and namespaces
|
||
- See: reference/language/using.md — `using` syntax, runner resolution, and style guidance.
|
||
|
||
Variables and scope
|
||
- See: reference/language/variables-and-scope.md — Block-scoped locals, assignment resolution, and strong/weak reference guidance.
|
||
|
||
Type system (SSOT)
|
||
- See: reference/language/types.md — runtime truthiness, `+`/compare/equality semantics, and the role/limits of MIR type facts.
|
||
|
||
Grammar (EBNF)
|
||
- See: reference/language/EBNF.md — Stage‑2 grammar specification used by parser implementations.
|
||
- Unified Members (stored/computed/once/birth_once): see reference/language/EBNF.md “Box Members (Phase 15)” and the Language Reference section. Default ON (disable with `NYASH_ENABLE_UNIFIED_MEMBERS=0`).
|
||
|
||
Member exceptions and handlers (Stage‑3)
|
||
- Postfix `catch/cleanup` may be attached to computed/once/birth_once/method blocks when Stage‑3 is enabled. Stored members (plain `name: Type [= expr]`) do not support handlers.
|
||
|
||
Related implementation notes
|
||
- Tokenizer: src/tokenizer.rs
|
||
- Parser (expressions/statements): src/parser/expressions.rs, src/parser/statements.rs
|
||
- MIR Lowering (expressions): src/mir/builder/exprs.rs and friends
|
||
|
||
Navigation tips
|
||
- The “reference/language/LANGUAGE_REFERENCE_2025.md” is the canonical long‑form reference; use the Cheat Sheet for quick syntax lookup.
|
||
- Phase 12.7 files capture the finalized sugar and new constructs (match (replaces peek), ternary, null‑safe).
|