User export distinct from runtime builtins

Platform spec ADR

User export distinct from runtime builtins

Back to Export and callbacks ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

Articles

• Callback registration Host registration table protocol for Beskid exports invoked from foreign code (v0.3). article Standard Reviewed Sat May 23
• Export attribute Normative Export metadata for pub functions exposed to foreign hosts (v0.3). article Standard Reviewed Wed May 20
• Export and callbacks — Verification and traceability Conformance fixtures for Export and callback registration (v0.3). article Standard Reviewed Sat May 23

History

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

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 3 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
  Export and callbacks

  Parent feature hub

Context

Plugin authors confused generated exports with frozen JIT builtin tables.

Decision

User export symbols are generated from Beskid compilation units. Frozen runtime builtin exports remain on beskid_abi / Rust ABI profile — export-only work must not change BESKID_RUNTIME_ABI_VERSION.

Consequences

Codegen plans export metadata beside ExternImport; trampolines use runtime TLS hooks.

Verification anchors

/platform-spec/language-meta/interop/export-and-callbacks/ implementation anchors.