hakorune/docs/development/roadmap/phases/phase-15/imports-namespace-plan.md

# Phase 15.3 — Imports/Namespace/nyash.toml Plan

Status: 15.3 planning; focus remains on Stage‑1/2 compiler MVP. This document scopes when and how to bring `nyash.toml`/include/import/namespace into the selfhost path without destabilizing parity.

Goals
- Keep runner‑level `nyash.toml` parsing/resolution as the source of truth during 15.3.
- Accept `using/import` syntax in the Ny compiler as a no‑op (record only) until resolution is delegated.
- Avoid VM changes; resolution happens before codegen.

Scope & Sequence (Phase 15.3)
1) Stage‑1/2 compiler stability (primary)
   - Ny→JSON v0 → Bridge → PyVM/llvmlite parity maintained
   - PHI merge remains on Bridge (If/Loop)
2) Imports/Namespace minimal acceptance (15.3‑late)
   - Parse `using ns` / `using "path" [as alias]` as statements in the Ny compiler
   - Do not resolve; emit no JSON entries (or emit metadata) — runner continues to strip/handle
   - Gate via `NYASH_ENABLE_USING=1`
3) Runner remains in charge
   - Keep existing Rust runner’s `using` stripping + modules registry population
   - `nyash.toml` parsing stays in Rust (Phase 15)

Out of scope (Phase 15)
- Porting `nyash.toml` parsing to Ny
- Cross‑module codegen/linking in Ny compiler
- Advanced include resolution / package graph

Acceptance (15.3)
- Ny compiler can lex/parse `using` forms without breaking Stage‑1/2 programs
- Runner path (Rust) continues to resolve `using` and `nyash.toml` as before (parity unchanged)

Looking ahead (MIR18 / Phase 16)
- Evaluate moving `nyash.toml` parsing to Ny as a library box (ConfigBox)
- Unify include/import/namespace into a single resolver pass in Ny with a small JSON side channel back to the runner
- Keep VM unchanged; all resolution before MIR build

Switches
- `NYASH_ENABLE_USING=1` — enable `using` acceptance in Ny compiler (no resolution)
- `NYASH_SKIP_TOML_ENV=1` — skip applying [env] in nyash.toml (existing)
-												🚀 Start Phase 15.3: Nyash compiler MVP implementation

Major milestone:
- Set up apps/selfhost-compiler/ directory structure
- Implement basic Nyash compiler in Nyash (CompilerBox)
- Stage-1: Basic arithmetic parser (int/string/+/-/*/括弧/return)
- JSON v0 output compatible with --ny-parser-pipe
- Runner integration with NYASH_USE_NY_COMPILER=1 flag
- Comprehensive smoke tests for PHI/Bridge/Stage-2

Technical updates:
- Updated CLAUDE.md with Phase 15.3 status and MIR14 details
- Statement separation policy: newline-based with minimal ASI
- Fixed runaway ny-parser-pipe processes (CPU 94.9%)
- Clarified MIR14 as canonical instruction set (not 13/18)
- LoopForm strategy: PHI auto-generation during reverse lowering

Collaborative development:
- ChatGPT5 implementing compiler skeleton
- Codex provided LoopForm PHI generation guidance
- Claude maintaining documentation and coordination

🎉 セルフホスティングの歴史的一歩！自分自身をコンパイルする日が近いにゃ！

Co-Authored-By: ChatGPT <noreply@openai.com>

											
										
										
											2025-09-15 01:21:37 +09:00
+								# Phase 15.3 — Imports/Namespace/nyash.toml Plan
 								Status: 15.3 planning; focus remains on Stage‑1/2 compiler MVP. This document scopes when and how to bring `nyash.toml`/include/import/namespace into the selfhost path without destabilizing parity.
 								Goals
 								- Keep runner‑level `nyash.toml` parsing/resolution as the source of truth during 15.3.
 								- Accept `using/import` syntax in the Ny compiler as a no‑op (record only) until resolution is delegated.
 								- Avoid VM changes; resolution happens before codegen.
 								Scope & Sequence (Phase 15.3)
 ) Stage‑1/2 compiler stability (primary)
 								   - Ny→JSON v0 → Bridge → PyVM/llvmlite parity maintained
 								   - PHI merge remains on Bridge (If/Loop)
 ) Imports/Namespace minimal acceptance (15.3‑late)
 								   - Parse `using ns` / `using "path" [as alias]` as statements in the Ny compiler
 								   - Do not resolve; emit no JSON entries (or emit metadata) — runner continues to strip/handle
 								   - Gate via `NYASH_ENABLE_USING=1`
 ) Runner remains in charge
 								   - Keep existing Rust runner’s `using` stripping + modules registry population
 								   - `nyash.toml` parsing stays in Rust (Phase 15)
 								Out of scope (Phase 15)
 								- Porting `nyash.toml` parsing to Ny
 								- Cross‑module codegen/linking in Ny compiler
 								- Advanced include resolution / package graph
 								Acceptance (15.3)
 								- Ny compiler can lex/parse `using` forms without breaking Stage‑1/2 programs
 								- Runner path (Rust) continues to resolve `using` and `nyash.toml` as before (parity unchanged)
-												📚 Phase 15 - セルフホスティング戦略の明確化とEXE-first実装

## 主な変更点

### 🎯 戦略の転換と明確化
- PyVMを開発ツールとして位置づけ（本番経路ではない）
- EXE-first戦略を明確に優先（build_compiler_exe.sh実装済み）
- Phase順序の整理: 15.2(LLVM)→15.3(コンパイラ)→15.4(VM)

### 🚀 セルフホスティング基盤の実装
- apps/selfhost-compiler/にNyashコンパイラMVP実装
  - compiler.nyash: メインエントリー（位置引数対応）
  - boxes/: parser_box, emitter_box, debug_box分離
- tools/build_compiler_exe.sh: ネイティブEXEビルド＋dist配布
- Python MVPパーサーStage-2完成（local/if/loop/call/method/new）

### 📝 ドキュメント整備
- Phase 15 README/ROADMAP更新（Self-Hosting優先明記）
- docs/guides/exe-first-wsl.md: WSLクイックスタート追加
- docs/private/papers/: 論文G～L、爆速事件簿41事例収録

### 🔧 技術的改善
- JSON v0 Bridge: If/Loop PHI生成実装（ChatGPT協力）
- PyVM/llvmliteパリティ検証スイート追加
- using/namespace機能（gated実装、Phase 15では非解決）

## 次のステップ
1. パーサー無限ループ修正（未実装関数の実装）
2. EXEビルドとセルフホスティング実証
3. c0→c1→c1'ブートストラップループ確立

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

Co-Authored-By: Claude <noreply@anthropic.com>

											
										
										
											2025-09-15 18:44:49 +09:00
+								Looking ahead (MIR18 / Phase 16)
-												🚀 Start Phase 15.3: Nyash compiler MVP implementation

Major milestone:
- Set up apps/selfhost-compiler/ directory structure
- Implement basic Nyash compiler in Nyash (CompilerBox)
- Stage-1: Basic arithmetic parser (int/string/+/-/*/括弧/return)
- JSON v0 output compatible with --ny-parser-pipe
- Runner integration with NYASH_USE_NY_COMPILER=1 flag
- Comprehensive smoke tests for PHI/Bridge/Stage-2

Technical updates:
- Updated CLAUDE.md with Phase 15.3 status and MIR14 details
- Statement separation policy: newline-based with minimal ASI
- Fixed runaway ny-parser-pipe processes (CPU 94.9%)
- Clarified MIR14 as canonical instruction set (not 13/18)
- LoopForm strategy: PHI auto-generation during reverse lowering

Collaborative development:
- ChatGPT5 implementing compiler skeleton
- Codex provided LoopForm PHI generation guidance
- Claude maintaining documentation and coordination

🎉 セルフホスティングの歴史的一歩！自分自身をコンパイルする日が近いにゃ！

Co-Authored-By: ChatGPT <noreply@openai.com>

											
										
										
											2025-09-15 01:21:37 +09:00
+								- Evaluate moving `nyash.toml` parsing to Ny as a library box (ConfigBox)
 								- Unify include/import/namespace into a single resolver pass in Ny with a small JSON side channel back to the runner
 								- Keep VM unchanged; all resolution before MIR build
 								Switches
 								- `NYASH_ENABLE_USING=1` — enable `using` acceptance in Ny compiler (no resolution)
 								- `NYASH_SKIP_TOML_ENV=1` — skip applying [env] in nyash.toml (existing)