Sibling articles under this feature previously restated requirements in inconsistent forms.
Analysis, query, and diagnostics facades - FAQ and troubleshooting
Platform spec article
Analysis, query, and diagnostics facades - FAQ and troubleshooting
Spec standingStandard
-
This feature hub owns normative MUST/SHOULD contract text for Analysis, query, and diagnostics facades.
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/analysis-query-diagnostics-facade/index.mdxarticle bundle under the same feature directory.
-
Platform-spec text supersedes informal crate comments for Analysis, query, and diagnostics facades.
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/analysis/compiler/crates/beskid_analysis/src/resolve/compiler/crates/beskid_lsp/src/diagnostics.rs
-
This feature hub defines the normative contract for **`Beskid.Compiler.Query`** and **`Beskid.Compiler.Diagnostics`** (a
Context
This feature hub defines the normative contract for
Beskid.Compiler.QueryandBeskid.Compiler.Diagnostics(and related analysis facades) and links detailed articles.Decision
The reference compiler must implement Analysis, query, and diagnostics facades as documented in this feature hub and its article bundle.
Consequences
Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
compiler/crates/beskid_analysis/src/analysis/compiler/crates/beskid_analysis/src/resolve/compiler/crates/beskid_lsp/src/diagnostics.rs
- Analysis, query, and diagnostics facades - Contracts and edge cases Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
- Analysis, query, and diagnostics facades - Design model Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
- Analysis, query, and diagnostics facades - Examples Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
- Analysis, query, and diagnostics facades - FAQ and troubleshooting Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
- Analysis, query, and diagnostics facades - Flow and algorithm Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
- Analysis, query, and diagnostics facades - Verification and traceability Semantic queries, symbol handles, and diagnostic transport available inside meta execution.
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 Analysis, query, and diagnostics facades.
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.