Skip to main content

Diagnostics

Diagnostic model and code ranges​

Jazz uses one structured diagnostic model for errors and warnings. Reports carry effective severity, a stable code, origin, summary, source labels, notes, and help. Warning promotion changes severity but keeps the W#### code and does not duplicate the report.

Type mismatch reports retain the expected and actual types until rendering. Within these reports, unknown variables are named t0, t1, and so on in first-occurrence order across both types. Repeated occurrences keep the same name; unrelated inference allocations do not change the displayed names. Names are local to each report.

Inference errors can include enclosing operations such as “while checking binding,” “while checking impl method,” and “while satisfying constraint.” Contexts are ordered from the innermost operation outwards, with duplicate contexts omitted. Adding context preserves a more specific primary location; unlocated errors use the enclosing operation's location.

RangeSubsystem
E0001–E0005syntax and Prelude preparation
E1001–E1010name and semantic analysis
E2001–E2019type inference and checking
E3001–E3040runtime evaluation and host operations
E4001–E4016module resolution, imports, and exports
E5001–E5005CLI, configuration, source input, and profiles

Pattern coverage uses two strict type diagnostics:

CodeMeaning
E2018a case or pattern lambda is non-exhaustive; the summary gives a witness
E2019an entire arm is unreachable after earlier unguarded arms

Guarded arms never contribute to exhaustiveness or shadow later arms. A guarded arm is still checked for reachability, so earlier unguarded arms can make it report E2019. Existing analysis or type errors suppress pattern-coverage follow-on reports.

Module diagnostic order​

Source loading, tokenization, and header/import syntax precede dependency resolution. Dependencies are resolved before parsing an importer's body, so a missing dependency can precede an unrelated body syntax error. Public export validation follows body and name discovery. Within each phase, source order and structured source locations are retained.

E4015 covers unavailable or conflicting export selections, including re-exports. Conflicting exports label the later selector and relate the earlier one. Imported operator collisions use the existing import diagnostic families; redeclaring or rebinding an imported operator is a module syntax error (E4004). Diagnostics show authored operator spellings.

Warning categories and IDs​

The warning catalog is:

CodeTokenStatus
W0001same-scope-rebindingemitted when enabled
W0002shadowing-outer-scopeemitted when enabled
W0003unused-bindingemitted for ordinary lexical-block bindings when enabled
W0004deprecated-syntaxreserved; no analyzer emitter

Warnings are off by default. Syntax rejected by the parser is an error, not a deprecation warning. CLI, environment, and config selection are described in the CLI reference.

Source ranges​

Source positions are one-based. Ranges have an exclusive end: hello at column 1 occupies columns 1 through 5 and ends at column 6. Columns follow the lexer's display convention: wide Unicode characters occupy two columns and other characters occupy one. Tabs advance to the next 8-column tab stop. A multiline range records both its ending line and column. Lexical ranges cover the original spelling, including quotes and escapes. Expression and pattern ranges exclude trailing whitespace and comments; list, tuple, and block nodes include their closing delimiter. Grouping parentheses have no separate AST node, so the enclosed node retains its range.

Structured compiler locations preserve endpoints through lowering, module qualification, and analysis. Synthetic locations may carry only a start position. Consumers can use sourceSpanEnd to distinguish these from complete ranges. The command-line renderer continues to print the primary start position.

Output and severity​

Standalone spans render as line:column; resolved module spans include the source path. Cross-module diagnostics can carry related locations. Compile errors suppress evaluation. Runtime errors suppress the final rendered value; warning-only runs still evaluate.