46fbe12ce6
feat(repl): Phase 288.1 session persistence + auto-display
...
実装内容:
- AST Rewriter (~430行): 未宣言変数を __repl.get/set に変換
- ExternCall Bridge: VM で __repl.get/set ハンドラー実装
- Rc<RefCell<>> セッション共有: VM と REPL runner 間で永続化
- 式自動表示: pure expression の結果を自動出力
- _ 変数: 最後の表示値を保存(Void は除外)
- .reset 実装: セッション変数の完全クリア
- Fail-Fast: 未定義変数読み取りで明示的エラー + ヒント
変更ファイル (8ファイル, +592行):
- src/runner/repl/ast_rewriter.rs (NEW, +430行)
- src/runner/repl/repl_runner.rs (+84/-35行)
- src/backend/mir_interpreter/handlers/externals.rs (+54行)
- src/mir/builder/calls/build.rs (+41行)
- src/backend/mir_interpreter/mod.rs (+12行)
- src/runner/repl/repl_session.rs (+11/-9行)
- src/runner/repl/mod.rs (+2行)
- src/runner/mod.rs (+2/-1行)
REPL専用設計(src/mir/builder/calls/build.rs の特別扱い理由):
- __repl.get/set は REPL mode 専用の橋渡し機能
- try_build_repl_method_call() で早期検出・ExternCall 変換
- file mode では決して使用されない(VM で "outside REPL mode" エラー)
- 将来的にも file mode への影響ゼロを保証
検証済み:
- 変数永続化: x = 42; print(x) → 42 ✅
- 式自動表示: 1 + 1 → 2 ✅
- _ 変数: 10 * 2 → 20; _ → 20 ✅
- Fail-Fast: 未定義エラー + ヒント ✅
- 回帰テスト: 154/154 PASS ✅
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-25 23:04:59 +09:00
c117a04035
fix(rewrite): toString normalization to BoxCall(slot #0 ) - Phase 287 P4
...
Root cause: toString/stringify/str were being rewritten to Global/Method calls
with class inference, causing Main.toString/0 to be called for primitives.
Fix (Box-First + Legacy Deletion):
1. ✅ MIR Builder - toString normalization (special.rs)
- ALWAYS emit BoxCall with method_id=0 for toString/stringify/str
- Do NOT rewrite to Global(Class.str/0) or Method calls
- DELETED 70+ lines of complex class inference logic
- Primitive guard with method name filter (known.rs)
2. ✅ JSON Serializer - method_id output (mir_json_emit.rs)
- Include method_id field in BoxCall JSON for LLVM
3. ✅ LLVM Backend - universal slot #0 support
- Extract method_id from JSON (instruction_lower.py)
- Box primitives via nyash.box.from_i64 (boxcall.py)
- Invoke toString via plugin system with method_id=0
- ⚠️ TODO: Add nyash.integer.tostring_h to kernel
Test Results:
✅ VM: local x = 1; print(x.toString()) → "1" (PASS)
✅ VM: array_length test (boxed Integer) → PASS
⚠️ LLVM: Compiles successfully, needs kernel function
SSOT: slot_registry - toString is ALWAYS universal slot #0
Legacy Deleted:
- special.rs: Complex class inference rewrite (~70 lines)
- special.rs: Unique suffix fallback for toString
- special.rs: Main box special handling
Files changed:
- src/mir/builder/rewrite/special.rs (try_early_str_like_to_dst)
- src/mir/builder/rewrite/known.rs (primitive guards x4)
- src/runner/mir_json_emit.rs (method_id serialization x2)
- src/llvm_py/builders/instruction_lower.py (method_id extraction)
- src/llvm_py/instructions/boxcall.py (slot #0 handler)
- docs/reference/language/quick-reference.md (toString SSOT)
🎊 Generated with Claude Code
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-25 11:38:05 +09:00
98a948344e
fix(rewrite): Add conservative primitive type guards to prevent toString() misrewrite (Phase 287 P4)
...
Root cause: x.toString() (x=Integer local var) was incorrectly rewritten to
Global(Main.toString/0) instead of using universal slot toString[#0 ].
The bug had two layers:
1. Early rewrite guards in special.rs correctly blocked it
2. BUT known.rs rewrite functions recursively called emit_unified_call with
Global("Main.toString/0"), bypassing the primitive type checks
Fix (Box-First Conservative Guards):
- Added primitive type guard (Integer/Float/Bool/String) to ALL 4 rewrite
functions in known.rs:
1. try_known_rewrite (line 56-69)
2. try_known_rewrite_to_dst (line 131-144)
3. try_unique_suffix_rewrite (line 243-256)
4. try_unique_suffix_rewrite_to_dst (line 283-296)
- Added debug trace in unified_emitter.rs to track CallTarget flow
Test case verification:
static box Main { main() { local x = 1; print(x.toString()) } }
Expected: "1" (via universal slot toString[#0 ])
Before: "Main()" (Global(Main.toString/0) misrewrite)
After: "1" (boxcall via Method slot #0 ) ✅
MIR verification:
Before: Global("Main.toString/0") in main function
After: boxcall instruction (universal slot) ✅
Files changed:
- src/mir/builder/rewrite/known.rs: 4 functions + primitive guard
- src/mir/builder/rewrite/special.rs: debug trace
- src/mir/builder/calls/unified_emitter.rs: debug trace
SSOT: docs/reference/language/types.md - toString() is universal slot #0
🎉 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-25 10:43:43 +09:00
cc05c37ae3
feat(phase285w): Phase 285W-Syntax-0.1 - Reject weak(...) syntax (Parser-level Fail-Fast)
...
- Parser guard: Reject weak(...) with LPAREN check in parse_unary()
- Error: "Use 'weak expr', not 'weak(expr)'" (helpful message)
- Location: src/parser/expressions.rs:248-256
- MIR builder guard: Defense-in-depth for any bypassed cases
- Location: src/mir/builder/calls/build.rs:37-46
- Rejection test: apps/tests/phase285w_weak_call_rejected.hako
- Smoke test: phase285w_weak_call_rejected_vm.sh (PASS ✅ )
- Documentation:
- EBNF.md: Add ~ (BitNot) to unary operators
- lifecycle.md: Document weak(expr) as invalid syntax
- phase-285/README.md: Add Phase 285W-Syntax-0.1 entry
Test results: 5/6 phase285 tests PASS (1 unrelated failure)
SSOT: docs/reference/language/lifecycle.md
Closes: Phase 285W-Syntax-0.1
2025-12-25 00:04:55 +09:00
9227673ef7
feat(phase285w): Implement weak x unary operator syntax
...
Phase 285W-Syntax-0: Migrate weak reference syntax from function call
to unary operator for consistency and clarity.
**Changes**:
- Parser: Add UnaryOperator::Weak variant and parse_unary() handling
- MIR: Lower UnaryOp::Weak to emit_weak_new() (reuses existing path)
- AST: Add Weak to UnaryOperator enum + Display/JSON support
- Tests: Migrate 8 files from `weak(x)` to `weak x` syntax
- 7 .hako test files updated
- 1 smoke test shell script updated
- Cleanup: Remove obsolete weak(x) parser/MIR special cases
- Docs: Update Phase 285 README
**Syntax Change**:
- Old: `local w = weak(x)` (function call)
- New: `local w = weak x` (unary operator)
**Validation**: All migrated phase285* smoke tests pass (4/4 relevant)
**SSOT**: docs/reference/language/lifecycle.md
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-24 17:21:21 +09:00
ab76e39036
feat(parser): Phase 285A1.4 & A1.5 - Weak field sugar + Parser hang fix
...
A1.4: Add sugar syntax `public weak parent` ≡ `public { weak parent }`
A1.5: Fix parser hang on unsupported `param: Type` syntax
Key changes:
- A1.4: Extend visibility parser to handle weak modifier (fields.rs)
- A1.5: Shared helper `parse_param_name_list()` with progress-zero detection
- A1.5: Fix 6 vulnerable parameter parsing loops (methods, constructors, functions)
- Tests: Sugar syntax (OK/NG), parser hang (timeout-based)
- Docs: lifecycle.md, EBNF.md, phase-285a1-boxification.md
Additional changes:
- weak() builtin implementation (handlers/weak.rs)
- Leak tracking improvements (leak_tracker.rs)
- Documentation updates (lifecycle, types, memory-finalization, etc.)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-24 07:44:50 +09:00
757193891f
feat(llvm/phi): Phase 277 P1 - fail-fast validation for PHI strict mode
...
## 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 >
2025-12-22 14:48:37 +09:00
4ef2261e97
fix(joinir): Phase 269 P1.2 - static call normalization for this.method()
...
Problem:
- `this.method()` calls in static box loops were using string constant "StringUtils" as receiver
- This violated Box Theory (static box this should not be runtime object)
- Pattern8 was trying to pass receiver to JoinIR, causing SSA/PHI issues
Solution (3-part fix):
1. **MeResolverBox Fail-Fast** (stmts.rs): Remove string fallback, error message cleanup
2. **ReceiverNormalizeBox** (calls/build.rs): Normalize `this/me.method()` → static call at compile-time
3. **Pattern8 Skip Static Box** (pattern8_scan_bool_predicate.rs): Reject Pattern8 for static box contexts
Key changes:
- **stmts.rs**: Update error message - remove MeBindingInitializerBox mentions
- **calls/build.rs**: Add This/Me receiver check, normalize to static call if current_static_box exists
- **calls/lowering.rs**: Remove NewBox-based "me" initialization (2 locations - fixes Stage1Cli regression)
- **pattern8_scan_bool_predicate.rs**: Skip Pattern8 for static boxes (use Pattern1 fallback instead)
Result:
- ✅ phase269_p1_2_this_method_in_loop_vm.sh PASS (exit=7)
- ✅ No regression: phase259_p0_is_integer_vm PASS
- ✅ No regression: phase269_p0_pattern8_frag_vm PASS
- ✅ Stage1Cli unit tests PASS
- ✅ MIR uses CallTarget::Global, no const "StringUtils" as receiver
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-22 03:33:30 +09:00
5f22fe8fcd
feat(pattern8): Phase 269 P1 - SSA fix and call_method type annotation
...
Phase 269 P1.0: Pattern8 SSA correctness
- Add PHI node for loop variable `i` in pattern8_scan_bool_predicate.rs
- Ensure proper SSA form: i_current = phi [(preheader, i_init), (step, i_next)]
- Create loop_predicate_scan.rs for Pattern8 Frag emission
- Pre-allocate PHI destination before block generation
- Use insert_phi_at_head_spanned() for span synchronization
Phase 269 P1.1: call_method return type SSOT propagation
- Add callee_sig_name() helper in annotation.rs for function name formatting
- Annotate call_method return types in emit_unified_call_impl()
- Use module signature as SSOT for return type resolution (no hardcoding)
- Arity-aware function name: "BoxName.method/arity"
Fixes: is_integer() now correctly returns Bool instead of String
Test: Simple call_method test returns exit=7 (loop test has pre-existing bug)
Unit tests: All 1389 tests passing
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-22 01:41:19 +09:00
4439d64da3
refactor(joinir): make jump_args layout explicit (Phase 256)
2025-12-20 13:04:24 +09:00
df23a52916
refactor(control_tree): modularize normalized_shadow dev pipeline
2025-12-18 08:14:49 +09:00
e0cbeb9aa0
feat(control_tree): Phase 129-B join_k as-last lowering
2025-12-18 07:53:27 +09:00
72f2c1f64d
feat(joinir/dev): Phase 126 wire available_inputs into normalized builder
...
- AvailableInputsCollectorBox::collect() called in lower_function_body (dev-only)
- try_lower_if_only() signature extended (accepts available_inputs)
- EnvLayout::from_contract() now uses real available_inputs (not empty stub)
- Unit tests updated (empty BTreeMap for backward compat)
- All 23 normalized_shadow tests PASS
2025-12-18 06:45:23 +09:00
cc1a0946b0
feat(joinir/dev): build Normalized if-only module with structure verification (no behavior change)
...
Phase 122 P2-P3: Dev-only wiring + structure verification
- Wire Phase 122 emission into existing Phase 121 dev path
- Add verify_normalized_structure() for module validation
- Check: phase, function count, entry point, env args count
- Strict mode: fail-fast on structure mismatch
- No behavior change to existing execution path
2025-12-18 04:52:09 +09:00
89b868703f
feat(joinir/dev): wire Phase 121 StepTree shadow lowering (strict fail-fast)
2025-12-18 04:34:43 +09:00
09ce24e132
feat(joinir): Phase 112 strict guard for StepTree required_caps
...
- Add control_tree_capability_guard.rs with check(tree, func_name, strict, dev)
- Allowlist: If, NestedIf, Loop, Return, Break, Continue
- Deny (strict): NestedLoop, TryCatch, Throw, Lambda, While, ForRange, Match, Arrow
- Wire into lower_function_body() (strict-only check)
- Error format: [joinir/control_tree/cap_missing/<Cap>] with 1-line Hint
- Unit tests: nested_loop_rejects, if_only_passes, strict_false_passes
- Default behavior unchanged (strict=false always Ok)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com >
2025-12-18 01:38:25 +09:00
e65bb791b9
refactor(builder): route debug logs via trace
2025-12-18 00:29:57 +09:00
2b5c141e22
feat(control_tree): add StepTree builder (dev-only)
2025-12-18 00:22:21 +09:00
e404746612
refactor(mir): Phase 139-P3-B - RoutingDecision を enum 対応 + レガシー削除
...
- RoutingDecision の missing_caps を Vec<CapabilityTag> に変更(型安全化)
- error_tags は to_tag() メソッドで自動生成
- 全 callsite を enum variant に修正
- capability_tags モジュール(文字列定数群)を完全削除
- 全テスト PASS(型安全性向上を確認)
- フォーマット適用
2025-12-16 07:02:14 +09:00
990d00393e
refactor(mir): Remove CompilationContext legacy fields (Phase 2-7/7) 🎉
...
Phase 2 完全完了!全 7 Context のレガシーフィールドを完全削除。
## Changes
- Migrated all access sites to comp_ctx.* (15 fields)
- Removed 15 deprecated fields:
* compilation_context
* current_static_box
* user_defined_boxes
* reserved_value_ids
* fn_body_ast
* weak_fields_by_box
* property_getters_by_box
* field_origin_class
* field_origin_by_box
* static_method_index
* method_tail_index
* method_tail_index_source_len
* type_registry
* current_slot_registry
* plugin_method_sigs
- Removed initialization code (15 field inits)
## Phase 2 完了!🎉
- builder.rs: 1222 → 1127 lines (-95 lines net)
- Deprecation warnings: 86 → 0 (完全排除)
- 全 36 deprecated fields 削除完了
- 全 14 sync helpers 削除完了
- 7 Context 完全SSOT化
## Tests
- cargo build --release: SUCCESS
- cargo test --release --lib: 1033/1033 PASS ✅
- Deprecation warnings: 0 ✅
Phase 2 Progress: 7/7 contexts complete (100%) ✅
- ✅ MetadataContext
- ✅ CoreContext
- ✅ TypeContext
- ✅ ScopeContext
- ✅ BindingContext
- ✅ VariableContext
- ✅ CompilationContext (this commit) 🎉
Phase 136 Context Box化: 完全完了!
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-16 04:07:17 +09:00
9170f0a85d
refactor(mir): Remove VariableContext legacy fields (Phase 2-6/7)
...
完全移行→削除の安全順序(Option C)に従い、VariableContext の
deprecated フィールドと sync helpers を完全削除。
## Changes
- Migrated all 66+ access sites to variable_ctx.variable_map
- Removed 1 deprecated field (variable_map) from MirBuilder
- Removed 2 sync helpers (sync_variable_ctx_to_legacy, sync_legacy_to_variable_ctx)
- Fixed BoxCompilationContext.variable_map references (kept as-is, different scope)
- Fixed ExitBindingBuilder.variable_map references (kept as-is, local field)
- Updated observer.rs to use variable_map() accessor method
## JoinIR Integration Verified
- CarrierInfo::from_variable_map() works correctly
- ExitLine contract maintained (Phase 132-135)
- NYASH_TRACE_VARMAP debug support preserved
- Pattern 1-5 lowering all functional
## Tests
- cargo test --release --lib: 1033 passed, 0 failed
- phase135_trim_mir_verify.sh: PASS (MIR SSA/ValueId OK)
- cargo build --release: SUCCESS
- Deprecation warnings: reduced (86 remaining, from other contexts)
## Statistics
- 27 files changed
- 146 insertions(+), 174 deletions(-)
- Net: -28 lines
Phase 2 Progress: 6/7 contexts complete (86%)
- ✅ MetadataContext
- ✅ CoreContext
- ✅ TypeContext
- ✅ ScopeContext
- ✅ BindingContext
- ✅ VariableContext (this commit)
- ⏳ CompilationContext (Phase 2-7 next)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-16 03:48:44 +09:00
7235fe62e9
refactor(mir): Remove ScopeContext legacy fields (Phase 2-4/7)
...
完全移行→削除の安全順序(Option C)に従い、ScopeContextの
deprecated フィールドと sync helpers を完全削除。
## Changes
- Migrated all access sites to scope_ctx.*
- Removed 7 deprecated fields:
- current_function
- lexical_scope_stack
- function_param_names
- loop_header_stack
- loop_exit_stack
- if_merge_stack
- debug_scope_stack
- Removed 2 sync helpers (sync_scope_ctx_to_legacy, sync_legacy_to_scope_ctx)
- Updated 20+ files with direct field access
## Tests
- cargo build --release: PASS ✅
- Deprecation warnings: 255 → 166 (-89, -35%)
Phase 2 Progress: 4/7 contexts complete (57%)
2025-12-15 23:41:30 +09:00
b92f85f993
refactor(mir): Remove TypeContext legacy fields (Phase 2-3/7)
...
完全移行→削除の安全順序(Option C)に従い、TypeContext の
deprecated フィールドと sync helpers を完全削除。
⚠️ 危険ゾーン: TypeFactsBox 等の同名フィールドと混同しないよう、
ファイル単位で手作業移行を実施。
## Changes
- Migrated all MirBuilder access sites to type_ctx.* (manual, 40+ files)
- Removed 3 deprecated fields (value_types, value_kinds, value_origin_newbox)
- Removed 2 sync helpers (sync_type_ctx_to_legacy, sync_legacy_to_type_ctx)
- Verified TypeFactsBox, CalleeGuardBox unchanged (no false positives)
## Tests
- cargo test --release --lib: 1029/1033 PASS
- TypeFactsBox integration: PASS (borrowed references unchanged)
- Deprecation warnings: 456 → 255 (-201, -44%)
## Safety Verification
✅ TypeFactsBox unchanged (still uses &'a BTreeMap borrowed references)
✅ CalleeGuardBox unchanged
✅ CalleeResolverBox unchanged
✅ BoxCompilationContext unchanged
Phase 2 Progress: 3/7 contexts complete (43%)
- ✅ MetadataContext
- ✅ CoreContext
- ✅ TypeContext (this commit)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-15 23:27:24 +09:00
3127ebb73d
feat(mir): Phase 136 Step 3/7 - ScopeContext extraction
...
## Summary
Extract scope and control flow management into ScopeContext for better organization.
## Changes
- **New file**: src/mir/builder/scope_context.rs (264 lines)
- Lexical scope stack management
- Control flow stacks (loop/if)
- Function context tracking
- Debug scope helpers
- **Updated**: src/mir/builder.rs
- Add scope_ctx field
- Mark legacy fields as deprecated
- Add sync helpers (sync_scope_ctx_to_legacy, sync_legacy_to_scope_ctx)
- **Updated**: src/mir/builder/vars/lexical_scope.rs
- Use scope_ctx as SSOT
- Sync to legacy fields for backward compat
- **Updated**: src/mir/builder/lifecycle.rs
- Sync current_function via scope_ctx
- **Updated**: src/mir/builder/calls/lowering.rs
- Sync function context in lowering flow
## Extracted Fields (7)
1. lexical_scope_stack - Block-scoped locals
2. loop_header_stack - Loop headers for break/continue
3. loop_exit_stack - Loop exit blocks
4. if_merge_stack - If merge blocks
5. current_function - Currently building function
6. function_param_names - Function parameters (for LoopForm)
7. debug_scope_stack - Debug region identifiers
## Test Results
- ✅ cargo build --release (291 warnings - deprecated usage)
- ✅ cargo test --release --lib - 1005/1009 PASS
- ✅ phase135_trim_mir_verify.sh - PASS
- ⚠️ phase132_exit_phi_parity.sh - Error (pre-existing issue)
## Progress
Phase 136: 3/7 Contexts complete (TypeContext, CoreContext, ScopeContext)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-15 20:28:21 +09:00
81d79161e4
feat(mir): Phase 136 Step 2/7 - CoreContext extraction complete
...
Extract core ID generation fields from MirBuilder to improve organization:
- value_gen: ValueIdGenerator
- block_gen: BasicBlockIdGenerator
- next_binding_id: u32 (Phase 74)
- temp_slot_counter: u32
- debug_join_counter: u32
Implementation:
- Created src/mir/builder/core_context.rs (215 lines)
- Added core_ctx field to MirBuilder as SSOT
- Deprecated legacy fields with backward compat
- ID allocation methods use core_ctx and sync legacy fields
- Added next_block_id() helper, replaced 30+ block_gen.next() calls
Testing:
- cargo build --release: SUCCESS (193 warnings expected)
- cargo test --release --lib: 1004/1004 PASS (+7 tests)
- phase135_trim_mir_verify.sh: PASS
- phase132_exit_phi_parity.sh: 3/3 PASS
Progress: 2/7 Context extractions complete (TypeContext + CoreContext)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com >
2025-12-15 20:10:36 +09:00
af6f95cd4b
Phase 33 NORM canon test: enforce normalized dev route for P1/P2/JP mini
2025-12-11 20:54:33 +09:00
32a91e31ac
feat(joinir): Phase 200-B/C/D capture analysis + Phase 201-A reserved_value_ids infra
...
Phase 200-B: FunctionScopeCaptureAnalyzer implementation
- analyze_captured_vars_v2() with structural loop matching
- CapturedEnv for immutable function-scope variables
- ParamRole::Condition for condition-only variables
Phase 200-C: ConditionEnvBuilder extension
- build_with_captures() integrates CapturedEnv into ConditionEnv
- fn_body propagation through LoopPatternContext to Pattern 2
Phase 200-D: E2E verification
- capture detection working for base, limit, n etc.
- Test files: phase200d_capture_minimal.hako, phase200d_capture_in_condition.hako
Phase 201-A: MirBuilder reserved_value_ids infrastructure
- reserved_value_ids: HashSet<ValueId> field in MirBuilder
- next_value_id() skips reserved IDs
- merge/mod.rs sets/clears reserved IDs around JoinIR merge
Phase 201: JoinValueSpace design document
- Param/Local/PHI disjoint regions design
- API: alloc_param(), alloc_local(), reserve_phi()
- Migration plan for Pattern 1-4 lowerers
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com >
2025-12-09 18:32:03 +09:00
440f8646b1
feat(joinir): Phase 183 LoopBodyLocal role separation + test fixes
...
Phase 183 Implementation:
- Added is_var_used_in_condition() helper for AST variable detection
- Implemented LoopBodyLocal filtering in TrimLoopLowerer
- Created 4 test files for P1/P2 patterns
- Added 5 unit tests for variable detection
Test Fixes:
- Fixed test_is_outer_scope_variable_pinned (BasicBlockId import)
- Fixed test_pattern2_accepts_loop_param_only (literal node usage)
Refactoring:
- Unified pattern detection documentation
- Consolidated CarrierInfo initialization
- Documented LoopScopeShape construction paths
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-12-08 23:43:26 +09:00
9d29718f03
fix(vm): Phase 173-B using-imported static box method calls
...
Enable static box method calls for boxes imported via `using` statement.
Root cause: 3 interrelated issues
1. Cross-function ValueId: methodize created singleton with ValueId that
can't be used across MIR function boundaries
2. Missing registration: using-imported static boxes weren't in
static_box_decls (only AST-based boxes were registered)
3. Wrong dispatch: method.rs tried InstanceBox dispatch instead of
MIR function table lookup for static boxes
Fixes:
- unified_emitter.rs: Use receiver=None for StaticCompiler boxes
- vm.rs: Auto-detect and register static boxes from MIR function names
- mod.rs: Add has_static_box_decl() helper
- method.rs: Add MIR function table lookup path for static boxes
- guard.rs: Trust methodize for StaticCompiler boxes without type info
Test: JsonParserBox.toString() via using import now works correctly
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-12-04 18:49:10 +09:00
466e636af6
Span trace utilities and runner source hint
2025-11-24 14:17:02 +09:00
2692eafbbf
feat(mir): Phase 26-H JoinIR型定義実装完了 - ChatGPT設計
...
## 実装内容(Step 1-3 完全達成)
### Step 1: src/mir/join_ir.rs 型定義追加
- **JoinFuncId / JoinContId**: 関数・継続ID型
- **JoinFunction**: 関数(引数 = φノード)
- **JoinInst**: Call/Jump/Ret/Compute 最小命令セット
- **MirLikeInst**: 算術・比較命令ラッパー
- **JoinModule**: 複数関数保持コンテナ
- **単体テスト**: 型サニティチェック追加
### Step 2: テストケース追加
- **apps/tests/joinir_min_loop.hako**: 最小ループ+breakカナリア
- **src/tests/mir_joinir_min.rs**: 手書きJoinIR構築テスト
- MIR → JoinIR手動構築で型妥当性確認
- #[ignore] で手動実行専用化
- NYASH_JOINIR_EXPERIMENT=1 トグル制御
### Step 3: 環境変数トグル実装
- **NYASH_JOINIR_EXPERIMENT=1**: 実験モード有効化
- **デフォルト挙動**: 既存MIR/LoopForm経路のみ(破壊的変更なし)
- **トグルON時**: JoinIR手書き構築テスト実行
## Phase 26-H スコープ遵守
✅ 型定義のみ(変換ロジックは未実装)
✅ 最小限の命令セット
✅ Debug 出力で妥当性確認
✅ 既存パイプライン無影響
## テスト結果
```
$ NYASH_JOINIR_EXPERIMENT=1 cargo test --release mir_joinir_min_manual_construction -- --ignored --nocapture
[joinir/min] MIR module compiled, 3 functions
[joinir/min] JoinIR module constructed:
[joinir/min] ✅ JoinIR型定義は妥当(Phase 26-H)
test result: ok. 1 passed; 0 failed
```
## JoinIR理論の実証
- **φノード = 関数引数**: `fn loop_step(i, k_exit)`
- **merge = join関数**: 分岐後の合流点
- **ループ = 再帰関数**: `loop_step` 自己呼び出し
- **break = 継続呼び出し**: `k_exit(i)`
## 次フェーズ (Phase 27.x)
- LoopForm v2 → JoinIR 自動変換実装
- break/continue ハンドリング
- Exit PHI の JoinIR 引数化
🌟 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
Co-Authored-By: ChatGPT <noreply@openai.com >
2025-11-23 04:10:12 +09:00
7812c3d4c1
feat(phi): Phase 25.1 - BTreeMap移行 (21ファイル、80%決定性達成)
...
## 修正内容
### Core MIR/PHI (5ファイル)
- builder.rs: variable_map, value_types, value_origin_newbox
- context.rs: 3つのマップ
- loop_builder.rs: 3箇所
- loop_snapshot_manager.rs: snapshot マップ
- loop_snapshot_merge.rs: 2箇所
### MIR関連 (4ファイル)
- function.rs: FunctionMetadata.value_types
- resolver.rs: CalleeResolverBox
- guard.rs: CalleeGuardBox
- loop_common.rs: apply_increment_before_continue
### JSON Bridge (5ファイル)
- json_v0_bridge/lowering.rs
- json_v0_bridge/lowering/expr.rs
- json_v0_bridge/lowering/if_else.rs
- json_v0_bridge/lowering/merge.rs
- json_v0_bridge/lowering/try_catch.rs
- json_v0_bridge/mod.rs
### Printer & Providers (4ファイル)
- printer.rs, printer_helpers.rs
- host_providers/mir_builder.rs
- backend/mir_interpreter/handlers/extern_provider.rs
### Tests (3ファイル)
- phi_core/conservative.rs
- tests/json_program_loop.rs
- tests/mir_stage1_using_resolver_verify.rs (2テスト有効化)
## テスト結果
- mir_stage1_using_resolver_resolve_with_modules_map_verifies: 80%成功率
- 完全な決定性は未達成 (HashMap 86箇所、HashSet 63箇所が残存)
🐱 Generated with Claude Code
2025-11-22 05:33:40 +09:00
c8ad1dae65
feat(naming): Phase 21.7++ Phase 3 完全達成 - Builder 側 StaticMethodId SSOT 統一
...
## 🎊 成果概要
**Phase 3: 全体統一** - MIR Builder 側を StaticMethodId 準拠に統一!
### ✅ 実装完了項目(全4タスク)
1. **素手 split 調査** (Phase 3.1)
- 調査結果: known.rs に2箇所のみ(split_once)
- unified_emitter には素手 split なし
- 置き換え対象: 2箇所のみで簡潔
2. **unified_emitter.rs 統一** (Phase 3.2)
- methodization 部分を StaticMethodId::parse() に変更
- decode_static_method() → StaticMethodId::parse()
- is_static_method_name() → StaticMethodId::parse().is_some()
- arity 判定を Optional 対応(None も許容)
3. **known.rs split_once 置き換え** (Phase 3.3)
- 2箇所の split_once('.') → StaticMethodId::parse()
- box_name 取得を構造化表現経由に統一
- コード削減: 8行 → 4行(50%削減)
4. **テスト実行・確認** (Phase 3.4)
- json_lint_stringutils_min_vm: PASS ✅
- namingbox_static_method_id: 13/13 PASS ✅
- ビルド成功、警告のみ(既存問題)
### 📊 技術的効果
- **素手 split 根絶**: 全箇所を StaticMethodId 経由に統一
- **コード品質向上**: 構造化表現で型安全化
- **保守性向上**: 名前パース処理が SSOT に集約
- **後方互換**: 既存機能に影響なし
### 🎯 Phase 4 への準備完了
- Builder/VM 両方が StaticMethodId SSOT 準拠
- ドキュメント整備のみ残存(2-3時間)
---
**Phase 0**: ✅ 完了 (Silent Failure 根絶)
**Phase 1**: ✅ 完了 (SSOT 基盤確立)
**Phase 2**: ✅ 完了 (VM 統一)
**Phase 3**: ✅ 完了 (Builder 統一)
**Phase 4**: 次のタスク (ドキュメント化)
🧮 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-22 02:43:45 +09:00
f4ae144559
fix(using): StringUtils using resolution - dual root cause fix
...
🎯 Phase 21.7++ - using StringUtils as StringUtils 完全動作化!
## Root Cause #1 : TOML Parse Error (lang/src/llvm_ir/hako_module.toml)
**Problem:**
```toml
line 18: aot_prep = "boxes/aot_prep.hako" # scalar
line 19: aot_prep.passes.strlen = "..." # table - CONFLICT!
```
→ TOML parse error prevented ALL aliases from loading
→ populate_from_toml() returned Err, aliases.len() = 0
**Fix:**
Commented out conflicting line 18:
```toml
# aot_prep = "boxes/aot_prep.hako" # Commented out: conflicts with aot_prep.passes.* below
aot_prep.passes.strlen = "boxes/aot_prep/passes/strlen.hako"
```
**Result:**
✅ populate_from_toml() succeeds
✅ 4 aliases loaded including StringUtils → string_utils
## Root Cause #2 : Missing Arity Suffix (src/backend/mir_interpreter/handlers/calls/global.rs)
**Problem:**
- MIR functions stored as "BoxName.method/arity"
- VM looked up "StringUtils.starts_with" (no arity)
- Function table had "StringUtils.starts_with/2" (with /2)
→ Lookup failed with "Unknown: StringUtils.starts_with"
**Fix:**
Auto-append arity from args.len() if missing:
```rust
let mut canonical = crate::mir::naming::normalize_static_global_name(func_name);
if !canonical.contains('/') {
canonical = format!("{}/{}", canonical, args.len());
}
```
**Result:**
✅ "StringUtils.starts_with" + args.len()=2 → "StringUtils.starts_with/2"
✅ VM function lookup succeeds
## Debug Infrastructure
**Added comprehensive debug logging:**
1. src/runner/pipeline.rs:36-55 - NYASH_DEBUG_USING=1 for alias loading
2. src/backend/mir_interpreter/handlers/calls/global.rs:17-42 - NYASH_DEBUG_FUNCTION_LOOKUP=1 for VM lookup
## Test Coverage
**src/tests/json_lint_stringutils_min_vm.rs:**
- Rewrote to test arity auto-completion (not using resolution)
- Inlined StringUtils implementation to avoid pipeline dependency
- Tests that VM can call "StringUtils.starts_with" without arity suffix
- ✅ Test passes
**CLI Verification:**
```bash
NYASH_PARSER_STAGE3=1 HAKO_PARSER_STAGE3=1 NYASH_DISABLE_PLUGINS=1 \
./target/release/hakorune apps/tests/json_lint_stringutils_min.hako
# Output: OK
# RC: 0
```
## Impact
- ✅ using StringUtils as StringUtils fully functional
- ✅ All using aliases load successfully
- ✅ VM can find functions with/without arity suffix
- ✅ No breaking changes to existing code
- ✅ Debug logging for future troubleshooting
## Files Modified
- lang/src/llvm_ir/hako_module.toml (TOML fix)
- src/runner/pipeline.rs (debug logging)
- src/backend/mir_interpreter/handlers/calls/global.rs (arity fix + logging)
- src/tests/json_lint_stringutils_min_vm.rs (rewrite + enable)
- src/tests/mod.rs (register test)
Co-authored-by: Task Agent <task@anthropic.com >
Co-authored-by: Claude Code <claude@anthropic.com >
2025-11-22 01:21:38 +09:00
b5cd05c27a
feat(mir): Phase 21.7 Step 3 - Methodization実装完了
...
🎯 Global("BoxName.method/arity") → Method{receiver=singleton} 変換
実装内容:
1. builder.rs: static_box_singletons フィールド追加
- BoxName → ValueId マッピングでシングルトン管理
2. unified_emitter.rs: methodization ロジック実装
- HAKO_MIR_BUILDER_METHODIZE=1 で有効化
- decode_static_method() でstatic box method判定
- singleton instance を NewBox で生成(キャッシュ済み)
- Callee::Global → Callee::Method 変換
動作確認:
- デフォルト(OFF): call_global Calculator.add/2 (既存挙動維持)
- トグル(ON): new Calculator → call %singleton.add (methodization)
- RC=0 両モード動作確認済み
テスト:
- apps/tests/phase217_methodize_test.hako 追加
- [methodize] Global(...) → Method{...} トレース出力
環境変数:
- HAKO_MIR_BUILDER_METHODIZE=1: methodization 有効化
- NYASH_METHODIZE_TRACE=1: 変換ログ出力
Phase 21.7 Step 3 完了!🎊
次: ドキュメント更新
2025-11-22 00:00:51 +09:00
a13f14cea0
feat(mir): Phase 21.7 Step 1-2 - NamingBox decode & Hotfix 7修正
...
## 実装内容
### Step 1: NamingBox decode関数追加 (naming.rs)
- ✅ `decode_static_method(func_name) -> Option<(box, method, arity)>`
- ✅ `is_static_method_name(func_name) -> bool`
- 対称性: encode ⇔ decode のペア実装で一貫性確保
### Step 2: unified_emitter Hotfix 7修正 (Lines 267-304)
- ✅ StaticCompiler box kind判定追加
- ✅ static box method は receiver 追加をスキップ
- ✅ instance method(RuntimeData/UserDefined)のみ receiver 追加
- ✅ トレース: NYASH_STATIC_METHOD_TRACE=1 でログ出力
## 判定ロジック
```rust
if box_kind == CalleeBoxKind::StaticCompiler {
// "BoxName.method/arity" 形式か確認
let func_name = format!("{}.{}/{}", box_name, method, args.len());
if is_static_method_name(&func_name) {
// static box method → receiver 追加しない
}
}
```
## 検証
✅ Stage-1 テスト: RC=0 (apps/tests/stage1_skip_ws_repro.hako)
✅ ビルド成功(0 error)
## 次のステップ
- Step 3: methodization実装 (HAKO_MIR_BUILDER_METHODIZE=1)
Co-Authored-By: ChatGPT5 <chatgpt@openai.com >
2025-11-21 23:52:10 +09:00
eb10fc7159
fix(mir): Phase 25.1 StaticCompiler receiver型推論バグ根治
...
## 問題
Stage-1ブリッジで `StringHelpers.skip_ws/2` 呼び出し時に:
- ParserBox.length(receiver=ValueId未定義) でVM落ち
- receiver が捏造される(型情報なし)
## 根本原因
1. CalleeResolver: receiver型なし→捏造ValueId生成
2. 順序問題: materialization → guard(逆であるべき)
3. 型注釈不足: String定数・BinOp結果に型情報なし
## 解決策(3 Phase)
### Phase 1: guard.rs Global フォールバック (lines 100-146)
- receiver型なし→Global変換で捏造ValueId防止
- Phase 3-C: 文字列メソッド→StringBox正規化追加
### Phase 2: unified_emitter.rs 順序反転 (lines 176-188)
- guard FIRST → materialization (Method のみ)
- Global 呼び出しの receiver 実体化を回避
### Phase 3-A: emit_string 型注釈 (constant.rs:46-49)
- String定数に value_types + value_origin_newbox 登録
### Phase 3-B: BinOp(Add) 型注釈強化 (ops.rs:70-86,145-166,178-198)
- value_origin_newbox もチェック(value_types のみ→両方)
- 結果も両方のマップに登録
### Phase 3-C: StaticCompiler 文字列メソッド正規化 (guard.rs:106-129)
- length/substring等→StringBox.method に統一
- ParserBox.length → StringBox.length
## 検証
✅ RC=0 達成(apps/tests/stage1_skip_ws_repro.hako)
✅ 正規化トレース確認(ParserBox→StringBox)
✅ receiver捏造完全防止
Co-Authored-By: ChatGPT5 <chatgpt@openai.com >
2025-11-21 13:53:50 +09:00
4565f7476d
wip(mir): StaticCompiler receiver正規化の部分的修正 - 将来の根治に向けた基盤整備
...
【修正内容】
1. src/mir/builder/calls/guard.rs
- receiver型情報がない場合のpass-through処理追加
- ME-CALL として後段処理に委譲
2. src/mir/builder/ssa/local.rs
- receiver kind で型情報がない場合、origin から型を推論
- value_types への伝播を強化
【現状】
- 完全な根治には至っていない(MIR builder設計レベルの複雑な依存関係)
- .hako側workaround (51d53c29 ) が実用的な解決策として機能中
【根本原因】
- value_origin_newbox に ParserBox が保持される
- value_types に実際の型(String等)が欠落
- receiver に型情報がないまま StaticCompiler Method に解決される問題
【今後の方向性】
- MIR builder の型伝播システム全体の見直しが必要
- Phase 25.1: Stage-1 bridge receiver bug (partial fix)
2025-11-21 13:28:35 +09:00
f9d100ce01
chore: Phase 25.1 完了 - LoopForm v2/Stage1 CLI/環境変数削減 + Phase 26-D からの変更
...
Phase 25.1 完了成果:
- ✅ LoopForm v2 テスト・ドキュメント・コメント完備
- 4ケース(A/B/C/D)完全テストカバレッジ
- 最小再現ケース作成(SSAバグ調査用)
- SSOT文書作成(loopform_ssot.md)
- 全ソースに [LoopForm] コメントタグ追加
- ✅ Stage-1 CLI デバッグ環境構築
- stage1_cli.hako 実装
- stage1_bridge.rs ブリッジ実装
- デバッグツール作成(stage1_debug.sh/stage1_minimal.sh)
- アーキテクチャ改善提案文書
- ✅ 環境変数削減計画策定
- 25変数の完全調査・分類
- 6段階削減ロードマップ(25→5、80%削減)
- 即時削除可能変数特定(NYASH_CONFIG/NYASH_DEBUG)
Phase 26-D からの累積変更:
- PHI実装改善(ExitPhiBuilder/HeaderPhiBuilder等)
- MIRビルダーリファクタリング
- 型伝播・最適化パス改善
- その他約300ファイルの累積変更
🎯 技術的成果:
- SSAバグ根本原因特定(条件分岐内loop変数変更)
- Region+next_iパターン適用完了(UsingCollectorBox等)
- LoopFormパターン文書化・テスト化完了
- セルフホスティング基盤強化
Co-Authored-By: Claude <noreply@anthropic.com >
Co-Authored-By: ChatGPT <noreply@openai.com >
Co-Authored-By: Task Assistant <task@anthropic.com >
2025-11-21 06:25:17 +09:00
1a406adc9d
feat(mir): Phase 26-A-3 パラメータ型情報自動登録完了
...
## ✅ 実装内容
- **setup_function_params()修正**:
- パラメータ登録時に型情報を自動付与
- `register_value_kind(pid, MirValueKind::Parameter(param_idx))`
- **借用競合回避**:
- param_kinds一時収集→一括登録パターン
- slot_regsと同じ安全な実装方式
## ✅ テスト結果
- **241テストPASS**: 既存機能に回帰なし
- 1失敗: mir_funcscanner_skip_ws (PHI nodeバグ、Phase 26-A-4で修正予定)
## 🎯 効果
関数パラメータが自動的に `MirValueKind::Parameter(idx)` として登録され、
`is_value_parameter(ValueId)` で型安全判定が可能に
## 📋 次のステップ
- Phase 26-A-4: loop_builder.rs修正(名前ベース→ValueIdベース判定)
- Phase 26-A-5: 統合テスト作成
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-20 09:40:18 +09:00
3a82633924
refactor(funcscanner): Region+next_i パターン統一 & SSA テスト追加
...
**FuncScanner .hako 側改善**:
- scan_all_boxes を Region + next_i 形式に統一(continue 多発による SSA/PHI 複雑さ削減)
- インデント修正(タブ→スペース統一)
- デバッグ print 削除
**SSA テスト追加**:
- lang/src/compiler/tests/funcscanner_scan_methods_min.hako
- src/tests/mir_funcscanner_ssa.rs (scan_methods & fib_min SSA デバッグテスト)
**Phase 25.3 ドキュメント**:
- docs/development/roadmap/phases/phase-25.3-funcscanner/ 追加
**関連**: Phase 25.3 FuncScanner 箱化準備作業
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-20 06:38:43 +09:00
a95fedf26a
fix(mir): Phase 25.1m - Continue PHI修正 & Bug A main(args)ループ修正
...
**Phase 25.1m: Continue PHI修正**
- seal_phis に continue_snapshots 入力を追加 (loopform_builder.rs)
- LoopShape::debug_validate に continue/break エッジ検証追加 (control_form.rs)
- test_seal_phis_includes_continue_snapshots テスト追加
- 実証テスト成功: balanced scan loop で 228回イテレーション確認
**Bug A修正: main(args) でループ未実行問題**
- LoopBuilder::build_loop で entry → preheader への jump 追加
- decls.rs でデュアル関数作成時のブロック接続修正
- mir_static_main_args_loop.rs テスト追加
**パーサー改善**:
- parser_box.hako に HAKO_PARSER_PROG_MAX ガード追加(無限ループ対策)
🎉 成果:
- Continue 文の PHI predecessor mismatch エラー完全解消
- main(args) パラメータ有りループが正常動作
- Stage-B balanced scan で continue 正常動作確認 (228回イテレーション)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-19 08:04:43 +09:00
5c5e1bd099
fix(mir): Hotfix 6+7 - Instance method receiver完全修正
...
問題箇所1 (Hotfix 6):
- setup_method_params が next_value_id() で新規 ValueId 生成
- でも MirFunction::new() で既に予約済み
- → パラメータマッピングがずれる(%2,%3 vs %0,%1)
修正1:
- 予約済み ValueId(0), ValueId(1), ... を直接使用
- setup_function_params と同じロジックに統一
問題箇所2 (Hotfix 7):
- emit_unified_call_impl で Callee::Method の receiver が args に含まれない
- finalize_call_operands は receiver を Callee 側に保持
- → VM の exec_function_inner で args = [] → ValueId(0) = Void
修正2:
- Callee::Method { receiver: Some(recv), .. } の場合に
args_local.insert(0, *recv) で receiver を先頭に追加
- VM のパラメータバインディングが正しく動作するように
検証:
- 手動テスト: ng → ok ✅
- 各種環境変数組み合わせでも動作確認済み
既知問題:
- userbox_birth_to_string_vm.sh スモークテストは依然失敗
→ 別調査が必要(手動では動作するので環境依存の可能性)
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-19 04:01:02 +09:00
c0fb1ccff8
fix(mir): Hotfix 6 - Instance method パラメータマッピング修正
...
問題:
- setup_method_params が next_value_id() を呼んで新しい ValueId を生成
- でも MirFunction::new() で既に ValueId 0..N が予約済み
- → パラメータが %2,%3 になり、シグネチャ %0,%1 とミスマッチ
修正:
- 予約済み ValueId を直接使用 (ValueId(0), ValueId(1), ...)
- setup_function_params と同じロジックに統一
影響:
- MyBox.birth/1 のパラメータマッピングが正しくなった
- %0 = me, %1 = v として正しく MIR 生成される
既知問題:
- user-defined box の実行時問題は残存(別調査が必要)
- dev verify の NewBox→birth 警告ロジック要調査
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-19 03:37:16 +09:00
b79697f137
feat(region): Phase 25.1l FunctionSlotRegistry完全実装
...
ChatGPT実装 M-1〜M-4:
- FunctionSlotRegistry: 変数スロット管理中央化
- RegionKind::Function追加
- RefKind分類統合
- 観測レイヤー完成
品質評価 (Task先生レビュー):
- 設計: ⭐ ⭐ ⭐ ⭐ ⭐ (箱理論完璧)
- 実装: M-1〜M-4全て完全
- 統合: 既存システムと高品質統合
- 影響: SSA/PHI非侵襲(観測専用)
既知問題:
- userbox_birth_to_string_vm失敗
→ 既存問題(Phase 25.1h以前から)
→ 本実装とは無関係
→ 別途調査予定
🤖 Generated with [Claude Code](https://claude.com/claude-code )
Co-Authored-By: Claude <noreply@anthropic.com >
2025-11-19 03:28:58 +09:00
39f5256c18
📊 Phase 25.1l: Region観測レイヤー骨格 + スコープ契約設計理解
...
**Region Box統一理論の実装開始**
新規追加:
- src/mir/region/mod.rs: Region/RefSlotKind型定義
- src/mir/region/observer.rs: Region観測レイヤー
- docs/development/roadmap/phases/phase-25.1l/: 設計ドキュメント
主要概念:
- Region Box = Function/Loop/If の統一箱
- RefSlotKind = GC管理用スロット種別(Strong/Weak/Borrowed/NonRef)
- 観測専用(NYASH_REGION_TRACE=1で動作、挙動変更なし)
設計理解の深化:
- ValueId(40)問題 = LoopForm v2スコープ契約違反の症状
- 根本解決 = Region観測で無名一時値のスコープまたぎを検出
- 箱理論3原則: 境界明確化/差し替え可能/段階的移行
関連議論:
- ChatGPT提案: Region統一理論でGC/寿命管理の基盤構築
- SlotRegistry: 変数の単一真実源(SSOT)
- 階層構造: FunctionRegion → LoopRegion → IfRegion
次のステップ:
- Phase 1: Region観測(現在)- 非破壊的追加
- Phase 2: メタデータ出力(MIR JSON拡張)
- Phase 3: GC統合(retain/release挿入)
テスト追加:
- lang/src/compiler/tests/stageb_mini_driver.hako
- tools/test_loopssa_breakfinder_slot.sh
Build: ✅ 全警告は既存のもの
Tests: 既存テスト全て緑維持
2025-11-19 02:44:40 +09:00
d3cbc71c9b
feat(mir): Phase 25.1f完了 - Conservative PHI + ControlForm観測レイヤー
...
🎉 Conservative PHI Box理論による完全SSA構築
**Phase 7-B: Conservative PHI実装**
- 片方branchのみ定義変数に対応(emit_void使用)
- 全変数にPHI生成(Conservative Box理論)
- Stage-1 resolver全テスト緑化(3/3 PASS)
**Phase 25.1f: ControlForm観測レイヤー**
- LoopShape/IfShape/ControlForm構造定義
- Loop/If統一インターフェース実装
- debug_dump/debug_validate機能追加
- NYASH_CONTROL_FORM_TRACE環境変数対応
**主な変更**:
- src/mir/builder/phi.rs: Conservative PHI実装
- src/mir/control_form.rs: ControlForm構造(NEW)
- src/mir/loop_builder.rs: LoopForm v2デフォルト化
**テスト結果**:
✅ mir_stage1_using_resolver_min_fragment_verifies
✅ mir_stage1_using_resolver_full_collect_entries_verifies
✅ mir_parserbox_parse_program2_harness_parses_minimal_source
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com >
Co-Authored-By: ChatGPT <chatgpt@openai.com >
2025-11-18 18:56:35 +09:00
fa087eeeea
✅ Hotfix 5: Pre-populate params vector in MirFunction::new()
...
📦 箱理論: Parameter ValueId完全予約システム確立
## 🎯 根本原因
Hotfix 4でnext_value_id counterは予約したが、paramsベクトルが空のまま。
setup_function_params()が新規ValueIdをインクリメント済みcounterから割り当て。
結果: シグネチャは%0だが本体は%2を使用するミスマッチ発生。
## ✅ 修正内容
### 1. src/mir/function.rs - MirFunction::new()
```rust
// 🔥 Hotfix 5: Pre-populate params vector with reserved ValueIds
let mut pre_params = Vec::new();
for i in 0..total_value_ids {
pre_params.push(ValueId::new(i));
}
// ...
params: pre_params, // ✅ Pre-populate instead of empty Vec
```
### 2. src/mir/builder/calls/lowering.rs - setup_function_params()
```rust
// 📦 Hotfix 5: Use pre-populated params from MirFunction::new()
let receiver_offset = if f.params.is_empty() { 0 } else {
if f.params.len() > params.len() { 1 } else { 0 }
};
for (idx, p) in params.iter().enumerate() {
let param_idx = receiver_offset + idx;
let pid = if param_idx < f.params.len() {
f.params[param_idx] // Use pre-allocated ValueId
} else {
let new_pid = f.next_value_id();
f.params.push(new_pid);
new_pid
};
// ...
}
```
## 📊 テスト結果
- ✅ mir_parserbox_parse_program2_harness_parses_minimal_source: PASS
- ✅ mir_stage1_using_resolver_full_collect_entries_verifies: PASS
- ⚠️ mir_stage1_using_resolver_min_fragment_verifies: 別問題(dominator violation)
## 🎉 成果
- **Parameter ValueId問題完全解決**: 0/3 → 2/3 tests passing
- **Counter予約とVector実体の完全一致**: シグネチャと本体の整合性確保
- **Static method receiver完全対応**: 暗黙receiverも正しく予約
## 🔧 次のステップ
残り1テストのdominator violation調査(LoopForm Exit PHI生成問題)
Co-Authored-By: task先生 <task@anthropic.com >
2025-11-18 07:56:47 +09:00
4ff9bd4791
refactor(builder): Phase 3-B,C完了 - 読みやすさ革命達成!
...
箱理論の完全実践:Call系処理を9個の専用箱で完全分離
- Phase 3-B: EffectsAnalyzerBox(エフェクト解析専用)
- Phase 3-C: CallMaterializerBox(Call前処理専用)
実装内容:
【Phase 3-B: EffectsAnalyzerBox】
1. 新規ファイル作成
- src/mir/builder/calls/effects_analyzer.rs (~155行)
- compute_call_effects: Calleeから副作用マスクを計算
- is_pure_method: Pureメソッド判定
- 5つのユニットテスト ✅
2. call_unified.rs整理
- compute_call_effects → 委譲に変更
- is_pure_method → 削除
- ~50行削減
【Phase 3-C: CallMaterializerBox】
1. 新規ファイル作成
- src/mir/builder/calls/materializer.rs (~151行)
- try_global_fallback_handlers: Global関数フォールバック
- materialize_receiver_in_callee: Receiver実体化
- Call前処理全般を集約
2. emit.rs整理
- 2つの大きな関数を委譲に変更
- ~115行削減
3. unified_emitter.rs更新
- CallMaterializerBox経由に変更
箱化効果(Phase 3全体):
【劇的な削減】
- emit.rs: 467行 → 164行(-303行、65%削減!)
- call_unified.rs: 144行 → 98行(-46行、32%削減!)
【新規箱(責務明確・読みやすい)】
- unified_emitter.rs: 250行(統一Call発行専用)
- effects_analyzer.rs: 155行(エフェクト解析専用)
- materializer.rs: 151行(Call前処理専用)
【読みやすさ革命】
- ✅ 500行超えファイル根絶(最大489行まで)
- ✅ 責務分離完璧(各ファイルが単一責務)
- ✅ 9個の専用箱で管理(guard/resolver/emitter/effects/materializer)
- ✅ テスト容易性劇的向上(独立した箱で簡単テスト)
Phase 3 最終状態:
- Phase 3-A: UnifiedCallEmitterBox ✅
- Phase 3-B: EffectsAnalyzerBox ✅
- Phase 3-C: CallMaterializerBox ✅
- 読みやすさ革命 ✅ 完全達成!
ビルド・テスト:
- cargo build --release: ✅ 成功
- effects_analyzer tests (5): ✅ all passed
- 既存機能互換性: ✅ 完全保持
2025-11-17 23:57:04 +09:00
9a4f05adac
refactor(builder): Phase 3-A - UnifiedCallEmitterBox実装完了
...
箱理論の実践:統一Call発行ロジックを独立した箱に集約
- 単一責務:統一Call発行のみ(Legacy Callは別モジュール)
- 状態レス:MirBuilderを引数で受け取る設計
- ピュア関数的:入力CallTarget → 解決・発行 → MirCall命令
実装内容:
1. 新規ファイル作成
- src/mir/builder/calls/unified_emitter.rs (~250行)
- UnifiedCallEmitterBox構造体
- 4つの主要メソッド:
* emit_unified_call (公開API)
* emit_unified_call_impl (コア実装)
* emit_global_unified (Global関数呼び出し)
* emit_value_unified (第一級関数呼び出し)
2. emit.rs からロジック移動
- emit_unified_call → 委譲に変更(1行)
- emit_unified_call_impl → 削除(~150行削減)
- emit_global_unified → 削除(委譲に変更)
- emit_value_unified → 削除(委譲に変更)
- try_global_fallback_handlers → pub(super)に変更
- materialize_receiver_in_callee → pub(super)に変更
3. mod.rs更新
- unified_emitter モジュール追加
箱化効果(Phase 3-A単独):
- emit.rs: 467行 → 261行(-206行、44%削減!)
- unified_emitter.rs: 250行(新規、Unified専用箱)
- 読みやすさ大幅向上:統一Call発行ロジックが独立
- 責務分離明確化:Legacy/Unifiedの完全分離
Phase 3 進捗:
- Phase 3-A: UnifiedCallEmitterBox ✅ 完了(本コミット)
- Phase 3-B: EffectsAnalyzerBox ⏳ 次の目標
- Phase 3-C: CallMaterializerBox ⏳ 最終目標
ビルド・テスト:
- cargo build --release: ✅ 成功
- 既存機能互換性: ✅ 完全保持
2025-11-17 23:49:18 +09:00