Nocter Development

This directory is the development root for Nocter. It contains the Rust bootstrap compiler, the tracked standard-library source, release packaging inputs, and implementation-facing documentation.

The user-facing language introduction and getting-started flow belong in the repository root README.md. The language specification belongs in ../spec. This directory documents development work only.

Quick Start

From the repository root:

./development/compiler/scripts/verify.sh

From this directory:

cargo test --manifest-path compiler/Cargo.toml

From development/compiler/:

cargo test

From the repository root, run a local Nocter program through the repository-local distribution image:

./development/compiler/scripts/package-local-release.sh
./dist/.nocter/nocter example.nct

Rust and Cargo are development-time dependencies. A released Nocter archive is intended to contain one .nocter/ home with a runnable nocter binary plus std/, without requiring Rust, LLVM, clang, as, ld, or an external runtime from users.

Developer Documents

• Compiler Docs Index: where each compiler document belongs.
• Architecture: compiler pipeline, module ownership, and phase boundaries.
• Implementation Status: current parsed, checked, buildable, runtime, CLI, std, and LSP capability.
• v0 Closure Definition: fixed completion gates for v0.
• Backend V0: native ARM64 Darwin backend and ABI lowering design.
• Std Runtime Status: implementation status of the tracked standard library and distributed std/ tree relative to the public spec.
• Interpolation Lowering: deferred lowering plan for bare string interpolation.
• Roadmap: recommended implementation order.
• Maintenance Policy: long-running development rules.
• TODO: short-term handoff state for the next compiler session.

Main Layout

.
├── README.md
├── AGENTS.md
├── TODO.md
├── compiler/
│   ├── Cargo.toml
│   ├── scripts/
│   ├── src/
│   └── tests/
├── std/
├── packaging/
└── docs/

• compiler/src/ contains the compiler implementation.
• compiler/tests/ contains user-visible CLI, runtime, distributed-home, LSP, and corpus integration tests.
• docs/ contains implementation-facing design and status documents.
• compiler/scripts/ contains developer verification and local release packaging helpers.
• std/ contains the canonical standard-library source.
• packaging/ contains release metadata copied into generated Nocter homes.