Design model

Platform spec article

Design model

Back to Corelib injection and resolution ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (4)

1. 0005-host-corelib-no-opt-out Host projects cannot opt out of corelib Accepted

   Parser rejects noCorelib and useCorelib false.

   Context

   Every host compilation must see the standard library graph.

   Decision

   Rule	Detail
   Forbidden keys	noCorelib, useCorelib: false rejected at parse
   Templates	Scaffolds must not emit opt-out keys

   Consequences

   Implicit injection in resolve_dependencies always attaches corelib.

   Verification anchors

   projects/parser.rs; template manifest tests.

   Open full ADR page

2. 0006-workspace-shard-cycle-guard Workspace shard cycle guard Accepted

   Corelib member packages must not implicit-back-link to aggregate.

   Context

   Shards under packages/* would create cycles if they gained implicit host edges.

   Decision

   Rule	Detail
   Guard	is_corelib_workspace_shard_manifest skips implicit back-edge
   Host	Only application hosts receive implicit corelib

   Consequences

   Building packages/runtime alone does not pull beskid_corelib as a hidden parent.

   Verification anchors

   resolver.rs; corelib workspace compile tests.

   Open full ADR page

3. 0007-mod-projects-exempt Mod projects exempt from host injection Accepted

   Compiler mods compile as carriers without host corelib rules.

   Context

   Mods are not end-user hosts; injecting corelib would distort mod graphs.

   Decision

   Rule	Detail
   Mod	Does not receive implicit host injection
   Host	Receives implicit corelib per D-CORE-COMP-0005

   Consequences

   Mod SDK projects declare their own dependency closure.

   Verification anchors

   Mod project tests in beskid_tests.

   Open full ADR page

4. 0008-cli-lsp-resolver-parity CLI and LSP resolver parity Accepted

   CLI and LSP share corelib discovery and graph options.

   Context

   IDE analysis must match CLI compilation attachment.

   Decision

   Rule	Detail
   CLI	ensure_corelib_ready before commands
   LSP	CompilationContext::try_for_analysis_path_with_graph_options

   Consequences

   Diagnostic drift between CLI and LSP indicates a resolver bug.

   Verification anchors

   LSP workspace tests; corelib/compile.rs.

   Open full ADR page

Articles

• Contracts and edge cases Corelib injection guarantees and edge cases. article Standard
• Design model How the compiler injects and resolves the corelib package into host compilations. article Standard
• Examples Observable corelib injection scenarios. article Standard
• FAQ and troubleshooting Corelib injection and resolution FAQ. article Standard
• Flow and algorithm End-to-end flow for corelib injection during project graph resolution. article Standard
• Verification and traceability Tests and traceability for corelib injection and resolution. article Standard

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 2 SpecSection(s) · 1 H2 heading(s)

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).

Related spec docs

• Feature
  Corelib injection and resolution

  Parent feature hub

• Feature
  Corelib discovery and packaging

  Canonical package identity and roots

Purpose

Host projects (Host, including template output) always receive an implicit dependency on the canonical corelib aggregate (beskid_corelib, package identity corelib). Injection happens during DAG construction in resolve_dependencies, not via optional manifest flags.

Injection model

flowchart TB
  Host[Host Project.proj]
  Resolver[resolve_dependencies]
  Std[Implicit Std / corelib path]
  Graph[Project DAG]
  Plan[CompilePlan]
  Sem[Semantic + lowering]
  Host --> Resolver
  Resolver --> Std
  Std --> Graph
  Graph --> Plan --> Sem

Input	Resolution
BESKID_CORELIB_ROOT	Points at workspace or install root containing beskid_corelib/Project.proj
Repo discovery	Walk ancestors for compiler/corelib/beskid_corelib
Explicit Std path dep	Honored when declared; path fallback uses default_corelib_dependency_path()
Corelib workspace shards	compiler/corelib/packages/* must not get implicit back-edge (cycle guard)

Manifest prohibitions

beskid_analysis projects/parser.rs rejects noCorelib and useCorelib: false at parse time. Templates and scaffolds must not emit opt-out keys.

Symbol resolution

After the graph attaches corelib nodes, semantic resolution treats corelib types and builtins like any other dependency assembly: same CompilationContext, same diagnostic catalog. User-visible names defer to language-meta; this feature covers graph attachment only.

CLI and LSP parity

ensure_corelib_ready in beskid_cli materializes bundled corelib before commands run. LSP uses the same resolver paths via CompilationContext::try_for_analysis_path_with_graph_options.

Implementation anchors

• compiler/crates/beskid_analysis/src/projects/graph/resolver.rs — default_corelib_dependency_path, is_corelib_workspace_shard_manifest
• compiler/crates/beskid_analysis/src/projects/parser.rs — opt-out rejection
• compiler/crates/beskid_cli/src/corelib_runtime.rs, build.rs
• Tests: compiler/crates/beskid_tests/src/projects/corelib/compile.rs