Runtime exposes C-compatible entrypoints

Platform spec ADR

Runtime exposes C-compatible entrypoints

Back to Rust ABI profile ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Rust ABI profile — Boundary and stability What is stable at the Rust runtime ↔ generated code boundary versus implementation-private Rust types. article Standard Reviewed Fri May 01
• Rust ABI profile — Shims and compatibility strategy How future Rust-native interop would layer on top of C ABI exports without breaking the stable runtime contract. article Proposed Reviewed Fri May 01

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

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

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).

Related spec docs

• Feature
  Rust ABI profile

  Parent feature hub

Context

JIT/AOT loaders need stable C symbol names while implementation remains Rust.

Decision

The Beskid runtime must expose stable C-compatible entrypoints to loaders. Rust-specific implementation choices must remain inside the runtime crate boundary.

Consequences

beskid_abi symbols and unwind bridges document the outward face only.

Verification anchors

compiler/crates/beskid_abi; compiler/crates/beskid_runtime.