Host projects cannot opt out of corelib
Platform spec ADR
Host projects cannot opt out of corelib
Spec standingStandard
- Contracts and edge cases Corelib injection guarantees and edge cases.
- Design model How the compiler injects and resolves the corelib package into host compilations.
- Examples Observable corelib injection scenarios.
- FAQ and troubleshooting Corelib injection and resolution FAQ.
- Flow and algorithm End-to-end flow for corelib injection during project graph resolution.
- Verification and traceability Tests and traceability for corelib injection and resolution.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
| Section id | Required | Found |
|---|---|---|
what-this-feature-specifies | yes | yes |
implementation-anchors | yes | yes |
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
Context
Section titled “Context”Every host compilation must see the standard library graph.
Decision
Section titled “Decision”| Rule | Detail |
|---|---|
| Forbidden keys | noCorelib, useCorelib: false rejected at parse |
| Templates | Scaffolds must not emit opt-out keys |
Consequences
Section titled “Consequences”Implicit injection in resolve_dependencies always attaches corelib.
Verification anchors
Section titled “Verification anchors”projects/parser.rs; template manifest tests.