Rendered from docs/obligations/0079-a-correctness-root-that-is-a-type-has-no-failing-fixture.md in the Headwater corpus. Every document on this half of the site is typed by the taxonomy the descriptor names: corpus.json.

A correctness root that is a type has no failing fixture

Context

Spec 12 asks each correctness root for conformance fixtures of its own. The rule behind that ask is that a check without a failing fixture does not ship.

Scope enforcement is a type now, and a document-scoped check that reaches for a sibling is a program the compiler refuses. A build that passes is not a fixture that fails.

Obligation

Nothing states what stands in for a failing fixture when the enforcement is a type.

Discharge

The instrument that fits is a test which asserts that a program does not compile, and no part of this specification asks for one.