CI and VSIX builds enable different beskid_runtime features. Confusing feature gates with ABI bumps breaks compatibility checks.
FAQ and troubleshooting
Platform spec article
FAQ and troubleshooting
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).
Do feature flags change beskid_runtime_abi_version?
Section titled “Do feature flags change beskid_runtime_abi_version?”No when behavior is backward compatible (RFF-001). Adding new optional symbols without old compilers calling them does not require a bump.
Why is array_new pointer null in the debugger?
Section titled “Why is array_new pointer null in the debugger?”Default builds omit arrays_backing. Enable the feature for tests that touch elements.
Where is extern_dlopen documented?
Section titled “Where is extern_dlopen documented?”Under Extern dispatch and policy — it is an engine feature, not a runtime Cargo feature.
Can users toggle features at run time?
Section titled “Can users toggle features at run time?”No. Selection is compile-time for the linked beskid_runtime artifact. CLI flags choose execution mode, not arrays_backing.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Fix |
|---|---|
| Array element segfault | Build runtime with arrays_backing or stop dereferencing ptr |
Missing rt_metrics_* at link | Enable metrics on runtime and ensure codegen emits calls |
| Extern works locally, fails in CI | CI engine lacks extern_dlopen — use link-time externs |
| VSIX vs local CLI array difference | Compare release matrices for runtime features |