Struct Lints 

pub struct Lints { /* private fields */ }

A run’s rule selection together with the -- htl: allow(...) comments of the sources it reports on: everything needed to decide whether a finding of the project layer is said.

lint.lua answers the same two questions for its own fifteen, inside report. This is the other half — the same allow syntax, read from the file a finding points into. The mechanism was never specific to Lua rules: an allow comment needs a line number and a rule name, and a project-layer finding has both.

A file is read at most once per run, and only when something was reported in it.

Implementations

impl Lints

pub fn new(sel: Selection) -> Self

A run over an already-built Selection. The allow-comment cache starts empty and fills as findings arrive, so a run that reports nothing reads no source.

pub fn parse(spec: &str) -> Result<Self>

The run’s selection from a +rule,-rule spec.

pub fn selection(&self) -> &Selection

The levels this run resolved to, for a caller that has to hand them somewhere else — the Lua side’s selection table, or a report of what a spec came to.

pub fn on(&self, rule: &str) -> bool

Whether this run reports rule at all. Ask before doing the work a rule needs: the contract rules type-check a module and scan a crate’s Rust sources, and a run that turned them off should pay for neither.

pub fn level(&self, rule: &str) -> Level

The level rule has for this run: what decides whether a finding under it fails the run, once it has been decided that the finding is said at all.

pub fn keep(&self, lines: Vec<String>) -> Vec<String>

The findings of lines this run says: the rest are a rule the run has off, or a site whose line allows the rule by name.

Text with no [htl <rule>] suffix is kept. Nothing the project layer produces is in that shape, and dropping a finding because its name could not be read would be the wrong way round.