Typed emitter and transforms - Contracts and edge cases

Platform spec article

Typed emitter and transforms - Contracts and edge cases

Back to Typed emitter and transforms ◎ Open feature in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs (3)

1. 0001-feature-hub-authority Feature hub authority Accepted

   This feature hub owns normative MUST/SHOULD contract text for Typed emitter and transforms.

   Context

   Sibling articles under this feature previously restated requirements in inconsistent forms.

   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/typed-emitter-and-transforms/index.mdx
   • article bundle under the same feature directory.

   Open full ADR page

2. 0002-spec-over-implementation-notes Specification over implementation notes Accepted

   Platform-spec text supersedes informal crate comments for Typed emitter and transforms.

   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/items/
   • compiler/crates/beskid_codegen/

   Open full ADR page

3. 0003-primary-contract-choice Primary contract for Typed emitter and transforms Accepted

   This feature hub defines the normative contract for **`Beskid.Compiler.Emit`** (typed emitter and transforms) and links

   Context

   This feature hub defines the normative contract for Beskid.Compiler.Emit (typed emitter and transforms) and links detailed articles.

   Decision

   The reference compiler must implement Typed emitter and transforms 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/syntax/items/
   • compiler/crates/beskid_codegen/

   Open full ADR page

Articles

• Typed emitter and transforms - Contracts and edge cases Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Thu Apr 30
• Typed emitter and transforms - Design model Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Fri May 01
• Typed emitter and transforms - Examples Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Thu Apr 30
• Typed emitter and transforms - FAQ and troubleshooting Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Thu Apr 30
• Typed emitter and transforms - Flow and algorithm Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Thu Apr 30
• Typed emitter and transforms - Verification and traceability Construction of syntax nodes and declarative transforms without raw text printing. article Standard Reviewed Thu Apr 30

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKfeature · 0 SpecSection(s) · 3 H2 heading(s)

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Feature
  Typed emitter and transforms

  Parent feature hub

This article states contracts and edge cases for Typed emitter and transforms.

Hard requirements

• Deterministic ordering — discovery and execution order must be reproducible from equal inputs (path-normalized roots, sorted files, stable tie-breaks).
• Bounded work — host enforces step limits, allocation caps, and recursion depth across nested meta calls.
• Versioned facades — Beskid.Compiler surface is tied to compiler language version tokens exposed on the compilation instance.

Edge cases

• Partial programs — facades must tolerate incomplete syntax where the language permits; diagnostics are preferred over host panics.
• Conflicting edits — multiple meta contributors touching the same declaration identity produce a deterministic merge failure surfaced as structured diagnostics.