Sibling articles under this feature previously restated requirements in inconsistent forms.
Syntax domain model generation - FAQ and troubleshooting
Platform spec article
Syntax domain model generation - FAQ and troubleshooting
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Syntax domain model generation.
Context
Decision
This feature hub owns normative MUST/SHOULD contract text. Sibling articles must not redefine hub requirements and should link here for authority.
Consequences
Contract changes start on the hub or in linked ADRs, then propagate to articles and implementation anchors.
Verification anchors
site/website/src/content/docs/platform-spec/compiler/compiler-mods/syntax-domain-model-generation/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Syntax domain model generation.
Context
Implementation crates accumulated informal notes that diverged from published contracts.
Decision
Normative platform-spec prose and ADRs under this feature supersede informal comments in implementation crates until explicitly migrated into spec text.
Consequences
Engineers file spec/ADR updates when behavior changes; crate comments are non-authoritative for conformance arguments.
Verification anchors
compiler/crates/beskid_analysis/src/syntax/compiler/crates/beskid_analysis/src/beskid.pestcompiler/crates/beskid_analysis/src/syntax/items/
-
Hand-maintained parallel syntax trees diverged from the host parser.
Context
Hand-maintained parallel syntax trees diverged from the host parser.
Decision
Canonical syntax model is generated via
beskid_ast_reflect_genintoBeskid.Compiler.*SDK sources from the Rust AST—aligned with D-INC-0006.Consequences
Mods consume generated facades; internal
beskid_analysis::syntaxremains host-only.Verification anchors
beskid_ast_reflect_gencompiler/crates/beskid_analysis/src/syntax/.
- Syntax domain model generation - Contracts and edge cases Contract for generating the immutable Beskid syntax domain model consumed by Mod SDK facades and meta discovery.
- Syntax domain model generation - Design model Contract for generating the immutable SyntaxMirror domain model consumed by Compiler Mod SDK facades.
- Syntax domain model generation - Examples Contract for generating the immutable Beskid syntax domain model consumed by Mod SDK facades and meta discovery.
- Syntax domain model generation - FAQ and troubleshooting Contract for generating the immutable Beskid syntax domain model consumed by Mod SDK facades and meta discovery.
- Syntax domain model generation - Flow and algorithm Contract for generating the immutable Beskid syntax domain model consumed by Mod SDK facades and meta discovery.
- Syntax domain model generation - Verification and traceability Contract for generating the immutable Beskid syntax domain model consumed by Mod SDK facades and meta discovery.
0 revisions (git unavailable at build; counts may be empty)
No commits recorded for this path.
Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).
This article collects FAQ entries for Syntax domain model generation.
Why separate language-meta and compiler pages?
Section titled “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?
Section titled “Can meta call arbitrary FFI?”No — unless explicitly granted by platform policy and declared in compilation capabilities. Default contracts deny ambient FFI.
Where do Roslyn/KSP parallels apply?
Section titled “Where do Roslyn/KSP parallels apply?”Only as rationale for incremental caches and typed models; Beskid contracts are authoritative here, not foreign tool behavior.