Shape of Errors to Come¶
Turner, J. (2016). Shape of Errors to Come.
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,
rustcprints 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 ahelp:line proposing a concrete next action, such as borrowing instead of moving or adding a missing trait boundThis 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.
Supported in partVerified against the source
- Where a traditional compiler emits "parse error" or a cryptic type mismatch,
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:f000a33811ee · see in the full table