RFCs
Design proposals for cross-cutting changes to neoc. Module-shaped changes are specced on the module reference pages directly under docs/src/<ns>/<name>.md; RFCs are for everything else — process, build, new namespaces, multi-module design, anything that does not fit on a single module page.
The full process is defined in RFC 0000 — Spec-driven development.
Status
Every RFC carries a status in its front matter. A draft banner is rendered at the top of any RFC that is not yet accepted, so readers of this site cannot mistake a proposal for the contract.
| Status | Meaning |
|---|---|
draft | Under refinement. Not the contract. May be edited freely. |
accepted | Merged. Awaiting implementation. |
implemented | Merged and the runtime is in line. |
rejected | Closed without acceptance. Kept for design history. |
superseded | Replaced by a later RFC. |
Index
Draft
Accepted
None yet.
Implemented
None yet.
Rejected
None yet.
Superseded
None yet.