Primary contract for Diagnostics parity (CLI and LSP)
Platform spec ADR
Primary contract for Diagnostics parity (CLI and LSP)
Spec standingStandard
- Diagnostics parity (CLI and LSP) - Contracts and edge cases Required parity behavior and accepted differences between diagnostic surfaces.
- Diagnostics parity (CLI and LSP) - Design model Provenance model for parse and semantic diagnostics across compiler surfaces.
- Diagnostics parity (CLI and LSP) - Examples Practical examples comparing CLI and LSP diagnostics for equivalent failures.
- Diagnostics parity (CLI and LSP) - FAQ and troubleshooting Troubleshooting mismatched diagnostics between command-line and editor surfaces.
- Diagnostics parity (CLI and LSP) - Flow and algorithm Diagnostic generation flow for CLI frontend, lowering, and LSP analysis paths.
- Diagnostics parity (CLI and LSP) - Verification and traceability Source anchors and tests used to prevent diagnostic drift between compiler surfaces.
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).
Context
Section titled “Context”This feature hub documents where diagnostics come from in CLI and LSP, and what differences are expected versus considered regressions.
Decision
Section titled “Decision”The reference compiler must implement Diagnostics parity (CLI and LSP) as documented in this feature hub and its article bundle.
Consequences
Section titled “Consequences”Changes require hub/ADR updates and verification anchor extensions.
Verification anchors
Section titled “Verification anchors”compiler/crates/beskid_analysis/