CI and VSIX builds enable different beskid_runtime features. Confusing feature gates with ABI bumps breaks compatibility checks.
Design model
Platform spec article
Design model
Spec standingStandard
-
Optional runtime capabilities toggle code paths without bumping BESKID_RUNTIME_ABI_VERSION.
Context
Decision
Concept Rule BESKID_RUNTIME_ABI_VERSIONChanges only on breaking layout/signature per D-EXEC-ABI-0002 Cargo featuresmetrics,arrays_backing,sched— build-time togglesAdditive exports New feature-gated symbols may ship without ABI bump if old artifacts never import them Shipped binaries Must document enabled features in release notes Tests Compiler tests enable features explicitly when validating optional paths Consequences
Mismatch (test expects
arrays_backing, default runtime does not) fails logically without ABI version inequality.Verification anchors
beskid_runtime/Cargo.toml; design model feature table. -
Without the feature, array_new may emit header-only arrays with null backing.
Context
Array lowering depends on whether the linked runtime allocates element storage behind
BeskidArrayheaders.Decision
arrays_backingBehavior Enabled array_newallocates element storage;ptrnon-null when length > 0Disabled Header-only arrays; ptrmay be nullABI Symbol list unchanged; semantics differ by build — document in release matrices Alignment Shipped CLI/VSIX should enable arrays_backingfor reference user workflowsConsequences
Conformance and doc tests must pin feature set when asserting array behavior.
Verification anchors
beskid_runtimearray_new; runtime JIT tests with feature flags.
- Contracts and edge cases MUST/SHOULD rules for optional runtime features and toolchain alignment.
- Design model Cargo feature gates, runtime build capabilities, and compiler alignment expectations.
- Examples Building runtime with features, array backing expectations, and engine extern_dlopen.
- FAQ and troubleshooting Optional runtime features vs ABI version, array backing surprises, and CI alignment.
- Flow and algorithm Selecting runtime features at build time and validating behavior at run time.
- Verification and traceability Cargo feature definitions, conditional compilation gates, and CI matrix expectations.
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).
Purpose
Section titled “Purpose”Document optional runtime capabilities selected at build time via Cargo features. These differ from BESKID_RUNTIME_ABI_VERSION: features toggle code paths without changing the baseline symbol list unless a feature adds new exports.
Primary actors
Section titled “Primary actors”| Actor | Role |
|---|---|
beskid_runtime Cargo.toml | Declares metrics, arrays_backing, sched features |
| Maintainers / CI | Builds runtime with agreed feature set for CLI, VSIX, releases |
| Compiler tests | Enable features when validating optional behavior |
| Tooling | Documents which flags are on in prebuilt binaries |
Feature catalog (reference tree)
Section titled “Feature catalog (reference tree)”| Feature | Effect |
|---|---|
arrays_backing | array_new allocates element storage; without it, header-only arrays (ptr = null) |
metrics | Extra rt_metrics_* exports for heap/alloc/event counters |
sched | Scheduler internals/experimental hooks (build-time; not user-facing) |
extern_dlopen (engine, not runtime) | Dynamic extern resolution — see Extern dispatch |
Alignment model
Section titled “Alignment model”flowchart LR manifest[Workspace / CI profile] rt[beskid_runtime features] tests[Compiler tests] cli[Shipped CLI / VSIX] manifest --> rt rt --> cli rt --> tests
Shipped artifacts must document enabled features. Mixing a compiler test build that expects arrays_backing against a default runtime produces logical failures without ABI version mismatch.