User Extern not arbitrary Rust crates

Platform spec ADR

User Extern not arbitrary Rust crates

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

Linking arbitrary rlib targets as user Extern would imply unstable Rust ABI across toolchains.

Decision

This profile is not a promise that arbitrary Rust crates can be user Extern targets without shims. User-authored foreign code on the supported path must remain C ABI profile until a future specification promotes additional Rust-native interop.

Consequences

Embedding docs steer authors to C contracts + shims for Rust libraries.

Verification anchors

/platform-spec/language-meta/interop/rust-abi-profile/ and FFI and extern.