ALL-ERRO0001 · swallowed_error
Count failures a declaration catches and then answers with nothing.
This is a deterministic rule for all languages. Read its implementation.
Definition
Section titled “Definition”Read every guard one declaration states and report each handler clause whose body does no
work. An empty body, a lone pass, a lone continue, and a lone ellipsis all say the same
thing, which is that the failure was seen and then dropped, so except ValueError followed by
pass in Python and an empty catch {} in TypeScript or C++ land here together. Where a
language hands failures back as values rather than throwing them, the same discard is written
as a binding to the throwaway name, and let _ = fallible() in Rust counts for that reason.
A dropped failure costs far more than the failure itself. Everything after the guard runs on state the failed step never finished writing, so the program carries on and produces a wrong answer confidently, and the person reading the logs a week later sees a clean run instead of the one line that would have named the cause.
Continue with evidence and references, or open the examples.