CI and VSIX builds enable different beskid_runtime features. Confusing feature gates with ABI bumps breaks compatibility checks.
Verification and traceability
Platform spec article
Verification and traceability
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).
Source files
Section titled “Source files”| Path | Content |
|---|---|
compiler/crates/beskid_runtime/Cargo.toml | [features] table |
compiler/crates/beskid_runtime/src/builtins/arrays.rs | #[cfg(feature = "arrays_backing")] |
compiler/crates/beskid_runtime/src/builtins/mod.rs | metrics module gate |
compiler/crates/beskid_engine/Cargo.toml | extern_dlopen feature |
compiler/crates/beskid_cli/src/commands/doc.rs | Execution modes referencing runtime |
| Suite | Notes |
|---|---|
beskid_tests/src/runtime/jit.rs | Default runtime feature set |
Engine extern_* tests | Require extern_dlopen |
Future: explicit arrays_backing fixture | Assert ptr != null when enabled |
Traceability
Section titled “Traceability”| ID | Check |
|---|---|
| RFF-001 | ABI version constant unchanged in feature-only PRs |
| RFF-003 | CI job definitions list arrays_backing where needed |
| RFF-006 | Default engine feature set off in release workflow |