User C ABI separate from runtime Rust exports

Platform spec ADR

User C ABI separate from runtime Rust exports

Back to FFI and extern ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Contract import syntax How extern contracts declare foreign imports and map to symbols and call shapes. article Standard Reviewed Wed May 20
• Extern attribute schema Normative Extern and per-method interop attributes for contract imports (v0.3). article Standard Reviewed Wed May 20
• FFI and extern — Verification and traceability Conformance strategy for v0.3 FFI spec (fixtures, diagnostics, ignored runtime tests). article Standard Reviewed Wed May 20

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

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

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  FFI and extern

  Parent feature hub

Context

Mixing user Extern symbols with BESKID_RUNTIME_ABI_VERSION exports caused namespace and stability risk.

Decision

Plane	Rule
User libraries	C ABI profile + link-time binding
Runtime embedding	Rust ABI profile / frozen builtin table
Separation	User Extern must not mutate runtime builtin symbol namespace

Consequences

JIT registration and engine policy keep tables disjoint; see profile boundary map on hub.

Verification anchors

compiler/crates/beskid_abi; Rust ABI profile; C ABI profile.