//! What a malformed rule file is told.
use fmt;
/// A place in a rule file and what is wrong there.
///
/// The compiler's own diagnostics carry a code, a caret and a source map, and none of that is
/// wanted here. A rule file is read by `cargo xtask rules` and its errors are read by whoever
/// is editing the rules, in a build log, so the shape that belongs here is the one every other
/// build tool prints: the file, the position, and one sentence. Spending a number out of the
/// compiler's diagnostic sequence on it would also be wrong, because those numbers are part of
/// what a user of the compiler can look up, and nobody compiling a C program will ever see one
/// of these.