arrays_backing gates array element storage
Platform spec ADR
arrays_backing gates array element storage
Spec standingStandard
- 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).
Context
Section titled “Context”Array lowering depends on whether the linked runtime allocates element storage behind BeskidArray headers.
Decision
Section titled “Decision”arrays_backing | Behavior |
|---|---|
| Enabled | array_new allocates element storage; ptr non-null when length > 0 |
| Disabled | Header-only arrays; ptr may be null |
| ABI | Symbol list unchanged; semantics differ by build — document in release matrices |
| Alignment | Shipped CLI/VSIX should enable arrays_backing for reference user workflows |
Consequences
Section titled “Consequences”Conformance and doc tests must pin feature set when asserting array behavior.
Verification anchors
Section titled “Verification anchors”beskid_runtime array_new; runtime JIT tests with feature flags.