Commit Graph

4 Commits

Author SHA1 Message Date
d7805e5974 feat(joinir): Phase 213-2 Step 2-2 & 2-3 Data structure extensions
Extended PatternPipelineContext and CarrierUpdateInfo for Pattern 3 AST-based generalization.

Changes:
1. PatternPipelineContext:
   - Added loop_condition: Option<ASTNode>
   - Added loop_body: Option<Vec<ASTNode>>
   - Added loop_update_summary: Option<LoopUpdateSummary>
   - Updated build_pattern_context() for Pattern 3

2. CarrierUpdateInfo:
   - Added then_expr: Option<ASTNode>
   - Added else_expr: Option<ASTNode>
   - Updated analyze_loop_updates() with None defaults

Status: Phase 213-2 Steps 2-2 & 2-3 complete
Next: Create Pattern3IfAnalyzer to extract if statement and populate update summary
2025-12-10 00:01:53 +09:00
466e636af6 Span trace utilities and runner source hint 2025-11-24 14:17:02 +09:00
b7c7e48526 feat(joinir): Phase 27.14 - FuncScannerBox._append_defs JoinIR lowering完了 + コード品質改善
## Phase 27.14: FuncScannerBox._append_defs/2 JoinIR lowering
- **新規実装**: `funcscanner_append_defs.rs` (322行)
  - Shared Builder Pattern採用
  - MIR-based lowering with CFG sanity checks
  - ValueId range 9000-10999 割り当て
- **テスト**: `mir_joinir_funcscanner_append_defs.rs` (3テスト)
  - type_sanity, empty_module_returns_none, auto_lowering (ignored)
- **最小.hako**: `funcscanner_append_defs_minimal.hako`

## コード品質改善 (5項目完了)
1. **CFG Sanity Checks強化** (`common.rs`)
   - `has_array_method()`: ArrayBox操作検出
   - `has_loop_increment()`: i+1パターン検出
2. **ValueIdテスト自動化** (`value_id_ranges.rs`)
   - マクロ化 + 自動overlap検証で30→15行に削減
3. **モジュール名統一確認** (作業不要、既に統一済み)
4. **Shared Builder命名統一** (`funcscanner_trim.rs`)
   - `build_trim_joinir` → `build_funcscanner_trim_joinir`
5. **全テストPASS確認**
   - value_id_ranges, funcscanner_trim, funcscanner_append_defs全てPASS 

## 効果
- CFG検証関数: 1個 → 3個 (200%↑)
- テストコード: 50%削減 (保守性向上)
- 命名一貫性: 75% → 100%
- ビルド成功率: 100%維持

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-24 05:23:26 +09:00
a554109b8e refactor(phase27.13): Introduce ValueId range management system
Introduce centralized ValueId range allocation to prevent ID conflicts
between lowering modules.

Changes:
1. New file: src/mir/join_ir/lowering/value_id_ranges.rs
   - Base address constants for each lowering module
   - Helper functions: entry(offset), loop_step(offset)
   - Range validation test: test_value_id_ranges_no_overlap

2. Range allocation (resolved conflict):
   - min_loop:              1000-2999 (entry: 1000+, loop: 2000+)
   - skip_ws:               3000-4999 (entry: 3000+, loop: 4000+)
   - funcscanner_trim:      5000-6999 (entry: 5000+, loop: 6000+)
   - stage1_using_resolver: 7000-8999 (entry: 7000+, loop: 8000+) ← CHANGED

3. Updated stage1_using_resolver.rs to use value_id_ranges helpers
   - ValueId(5000) → vid::entry(0)  // 7000
   - ValueId(6000) → vid::loop_step(0)  // 8000

4. Updated lowering/mod.rs to include value_id_ranges module

Results:
-  Build success (warnings only, no errors)
-  Tests: 2/2 existing tests pass (type_sanity, empty_module_returns_none)
-  value_id_ranges test pass (range overlap validation)
-  ValueId conflict resolved (trim vs stage1_using_resolver)

Benefits:
- Centralized range management prevents conflicts
- Type-safe: const fn for compile-time calculation
- Self-documenting: comments clarify ranges
- Easy extension: future lowerings can use 9000+, 11000+, etc.
2025-11-24 03:58:30 +09:00