conformance

Stack Conformance Suite

This directory contains implementation-independent compiler, formatter, and language-intelligence conformance cases for the Stack language.

Layout

Each case is a directory with a lowercase ASCII identifier:

valid/<case-id>/source.stack
valid/<case-id>/expected.ir.json
valid/<case-id>/expected.diagnostics.json  # optional

invalid/<case-id>/source.stack
invalid/<case-id>/expected.diagnostics.json

formatter/<case-id>/input.stack
formatter/<case-id>/expected.stack
formatter/<case-id>/expected.ir.json

language-intelligence/<case-id>/source.stack
language-intelligence/<case-id>/fixture.json

source.stack must be read as bytes. This permits future encoding-error fixtures even though valid Stack documents are UTF-8.

Expected IR documents conform to normalized-ir.schema.json. Diagnostic expectation documents conform to diagnostic-expectations.schema.json.

The canonical suite covers every Stack 1.0 diagnostic assigned to compiler stages 1 through 4: STK1001 through STK3014, excluding unassigned numbers, plus STK4002 and STK4003. validate-compiler-diagnostics.py verifies that every required code occurs in at least one expectation document. Renderer-stage STK4001, STK5001, and STK6001 remain outside compiler conformance.

The encoding cases intentionally include raw invalid UTF-8, a UTF-8 byte order mark, CRLF line endings, and a Unicode scalar before an error position. Tools must preserve source.stack bytes rather than decoding and rewriting fixtures during discovery.

Formatter inputs are compiler-valid Stack documents. A formatter runner compares canonical source bytes, formats the expected source again to verify idempotence, and compiles both input and expected source to verify that each is semantically equal to expected.ir.json. The complete formatter behavior is defined in the Stack Canonical Formatter Specification.

Language-intelligence fixtures contain ordered protocol-neutral request / expected-response pairs. They cover diagnostics, context-aware completion, caller-owned icon catalogs, hover, nested document symbols, incomplete syntax, and canonical format edits. Native and WebAssembly adapters consume the same files and pin the exact specification revision. The complete operation, recovery, ownership, and incremental-boundary behavior is defined in the Stack Language Intelligence Specification.

Comparison

• JSON values are compared semantically; formatting and object-member order do not matter.
• Array order is significant.
• A valid case must produce the expected normalized IR.
• An absent valid-case diagnostic file means no portable diagnostics are expected.
• An invalid case must not produce normalized IR.
• Diagnostic expectations compare code, severity, and range in emitted order. A fixture may also require exact expected values and ordering.
• Diagnostic message, help, and related-information wording are not compared.
• Language-intelligence request and response versions and features must match, all ranges belong to the source snapshot, and arrays retain fixture order.

The complete normative behavior is defined in the Stack Compiler Interchange Specification, Stack Canonical Formatter Specification, and Stack Language Intelligence Specification.