Shape of Errors to Come

Turner, J. (2016). Shape of Errors to Come.

Type

Web resource

Intellectual base

Web

Year

2016

Link

no authoritative link yet

Cited by

1 citation across 1 artifact.

Each citation links to the sentence it supports in the citing article.

Domain-specific

• Error-Message Opacity
  • Where a traditional compiler emits "parse error" or a cryptic type mismatch, rustc prints the offending source span with a caret, states the cause in plain terms (for example, that a value was moved and then used again), and — crucially — appends a help: line proposing a concrete next action, such as borrowing instead of moving or adding a missing trait bound

    This sourceThe Rust blog post announcing the redesigned compiler error format, built on the principle of putting the user's own source code front and centre with caret-underlined spans and labelled prose explanations; the suggestion ("help:") lines came later and are not shown here. Rust's own announcement of the rewritten diagnostics, stating the design intent directly; the Elm half of the sentence rests on Czaplicki's compiler-error post, cited alongside it.

Verification

This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.

Registry ID ref:f000a33811ee · see in the full table