Roadmap search
Versions, deliverables, workstreams, tasks, and pages
mod host bridge - FAQ and troubleshooting
src/content/docs/platform-spec/compiler/compiler-mods/mod-host-bridge/faq-and-troubleshooting.mdx
import SpecArticleChrome from '@beskid/beskid-ui/platform-spec/SpecArticleChrome.astro';
<SpecArticleChrome />This article collects FAQ entries for mod host bridge.
Why separate language-meta and compiler pages?
Language-meta defines Beskid-side mod contracts; this compiler area defines how the Rust host executes them safely and incrementally.
Can meta call arbitrary FFI?
No — unless explicitly granted by platform policy and declared in compilation capabilities. Default contracts deny ambient FFI.
Authoritative split: FFI and extern (language Extern contracts), Interop.Contracts (abstract primitives), C ABI profile / Rust ABI profile (concrete profiles). Meta does not implicitly satisfy any of these without host-granted capabilities.
Where do Roslyn/KSP parallels apply?
Only as rationale for incremental caches and typed models; Beskid contracts are authoritative here, not foreign tool behavior.