docs: update references after module splits

This commit is contained in:
2025-12-27 21:43:47 +09:00
parent 7ab042ca91
commit ed68e48ed1
23 changed files with 41 additions and 45 deletions

View File

@ -190,7 +190,7 @@ pub struct LoopShape {
**Nesting information exists ONLY in StepTree** (AST level):
```rust
// src/mir/control_tree/step_tree.rs (line 17-25)
// src/mir/control_tree/step_tree/mod.rs (line 17-25)
pub struct StepTreeFeatures {
pub max_loop_depth: u32, // ← Detected during AST → StepTree conversion
// ...

View File

@ -122,7 +122,7 @@ Still deferred to Phase 188.3+:
- **Phase 188.1 Reality**: `docs/development/current/main/phases/phase-188.1/README.md` § Implementation Reality
- **LoopRegion Definition**: `src/mir/control_form.rs` (lines 40-62)
- **StepTreeFeatures Definition**: `src/mir/control_tree/step_tree.rs` (lines 17-25)
- **StepTreeFeatures Definition**: `src/mir/control_tree/step_tree/mod.rs` (lines 17-25)
- **LoopForm/LoopShape Definition**: `src/mir/loop_form.rs`, `src/mir/control_form.rs`
---

View File

@ -16,7 +16,7 @@ SSOT (design): `docs/development/current/main/design/edgecfg-fragments.md`
- `if_``join_frag: Frag` を受け取り、Normal が「join 以降」を表すようにする
## 主要ファイル
- `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- `src/mir/builder/control_flow/edgecfg/api/frag.rs`
- `src/mir/builder/control_flow/edgecfg/api/edge_stub.rs`
- `src/mir/builder/control_flow/edgecfg/api/verify.rs`

View File

@ -15,7 +15,7 @@ SSOT (design): `docs/development/current/main/design/edgecfg-fragments.md`
- `wires` は Jump/Return 専用のまま維持
- `src/mir/builder/control_flow/edgecfg/api/frag.rs`
- `compose::if_` が header→then/else の `BranchStub` を生成するように更新
- `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- `emit_frag(function, frag)` を追加SSOT
- `verify_frag_invariants_strict()` を最初に実行
- `wires``emit_wires()` を内部利用

View File

@ -110,7 +110,7 @@ The LLVM harness consumes MIR JSON emitted by the Rust runner.
If `TypeOp` is missing in that JSON, the harness will never see it (and the JSON can become invalid due to missing defs).
Checklist:
- `src/runner/mir_json_emit.rs` must emit `{"op":"typeop", ...}` in **both** emitters:
- `src/runner/mir_json_emit/mod.rs` must emit `{"op":"typeop", ...}` in **both** emitters:
- `emit_mir_json_for_harness` (nyash_rust::mir) ✅ already supports TypeOp
- `emit_mir_json_for_harness_bin` (crate::mir) ⚠️ ensure TypeOp is included

View File

@ -94,7 +94,7 @@ Status: ✅ done (2025-12-22)
Artifacts:
- Kernel type check helper: `crates/nyash_kernel/src/lib.rs` (`nyash.any.is_type_h`)
- LLVM TypeOp lowering: `src/llvm_py/instructions/typeop.py`
- MIR JSON emission fix (bin): `src/runner/mir_json_emit.rs` (emit `op:"typeop"`)
- MIR JSON emission fix (bin): `src/runner/mir_json_emit/mod.rs` (emit `op:"typeop"`)
- Fixture (LLVM-safe): `apps/tests/phase274_p2_typeop_primitives_only.hako`
- Smoke (LLVM): `tools/smokes/v2/profiles/integration/apps/phase274_p2_typeop_is_as_llvm.sh`

View File

@ -123,7 +123,7 @@
#### B1: Document compose.rs Entry Points
**File**: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
**File**: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
**Changes Required**:
1. Add module-level documentation explaining:
@ -143,7 +143,7 @@
#### B2: Verify Composition API Implements Contract
**File**: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
**File**: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
**Action**: Documentation-only verification (checklist)
@ -173,7 +173,7 @@
#### B3: Add Tests for Composition Invariants
**File**: `src/mir/builder/control_flow/edgecfg/api/compose.rs` (test module)
**File**: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs` (test module)
**Action**: Gap analysis + add tests if needed
@ -391,7 +391,7 @@ tools/smokes/v2/run.sh --profile quick
### Phase B (Code: API)
4. `src/mir/builder/control_flow/edgecfg/api/compose.rs`
4. `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
### Phase C (Code: Pattern Prep - Documentation-only)

View File

@ -9,7 +9,7 @@ Goal:
## SSOT References
- Frag/emit SSOT: `docs/development/current/main/design/edgecfg-fragments.md`
- Composition SSOT: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- Composition SSOT: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- Plan line SSOTPattern6/7: `docs/development/current/main/phases/phase-273/README.md`
- Phase 280positioning: `docs/development/current/main/phases/phase-280/README.md`
@ -170,4 +170,3 @@ cleanup(Normal) を追加し、normalize_scan_with_init() の step back-edge を
- 新しい env var の追加はしない
- by-name hardcode での一時しのぎはしない
- `emit_frag()` 以外で terminator を生成しない

View File

@ -9,7 +9,7 @@ Goal:
## SSOT References
- Frag/emit SSOT: `docs/development/current/main/design/edgecfg-fragments.md`
- Composition SSOT: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- Composition SSOT: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- JoinIR overview: `docs/development/current/main/joinir-architecture-overview.md`
- Plan linePattern6/7: `docs/development/current/main/phases/phase-273/README.md`
- Composition adoptionPattern6/7: `docs/development/current/main/phases/phase-281/README.md`
@ -95,7 +95,7 @@ CFG構築は以下に収束させる
- lower() は必ず re-extract して SSOT 強制(二重検証)
**SSOT 参照**:
- Frag composition: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- Frag composition: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- Plan line: `src/mir/builder/control_flow/plan/normalizer.rs`
- Terminator 生成: `emit_frag()` (Phase 267)

View File

@ -23,7 +23,6 @@
- `docs/development/current/main/phases/phase-284/README.md`
- `docs/development/current/main/design/edgecfg-fragments.md`
- `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- `src/mir/builder/control_flow/edgecfg/api/emit.rs`
- `docs/development/current/main/phases/phase-282/README.md`

View File

@ -10,7 +10,7 @@ Status: P1 Complete (2025-12-23)
## SSOT References
- Frag/ExitKind 設計: `docs/development/current/main/design/edgecfg-fragments.md`
- Composition API: `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- Composition API: `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- Terminator emission: `src/mir/builder/control_flow/edgecfg/api/emit.rs``emit_frag()`
- Router SSOTSSOT=extract / safety valve: `docs/development/current/main/phases/phase-282/README.md`
@ -53,7 +53,7 @@ Phase 284 の完了条件は「`return` を含むケースが close-but-unsuppor
- 入口: `src/mir/builder/control_flow/joinir/patterns/router.rs`route=plan
- SSOT:
- `src/mir/builder/control_flow/plan/normalizer.rs`Frag 構築: branches/wires/exits
- `src/mir/builder/control_flow/edgecfg/api/compose.rs`(合成 SSOT
- `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`(合成 SSOT
- `src/mir/builder/control_flow/edgecfg/api/emit.rs``emit_frag()` terminator SSOT
- ここでは `return` を **Return edgeExitKind::Return**として組み立てるのが自然。

View File

@ -31,7 +31,7 @@ Phase 286 では JoinIR line を “第2の lowerer” として放置せず、*
- `src/mir/builder/control_flow/joinir/merge/mod.rs`
- Plan/Frag SSOT収束先:
- `src/mir/builder/control_flow/plan/*`
- `src/mir/builder/control_flow/edgecfg/api/compose.rs`
- `src/mir/builder/control_flow/edgecfg/api/compose/mod.rs`
- `src/mir/builder/control_flow/edgecfg/api/emit.rs`
## Scope提案