Struct SuppressionContext 

pub struct SuppressionContext<'a> { /* private fields */ }

Suppression context that tracks which suppressions are consumed by detectors.

Wraps the per-file suppression map and records, via AtomicBool flags, which suppression entries actually matched an issue during detection. After all detectors run, find_stale() returns unmatched suppressions.

Uses AtomicBool (not Cell<bool>) so the context can be shared across threads if detectors ever use rayon internally.

Implementations

impl<'a> SuppressionContext<'a>

pub fn new(modules: &'a [ModuleInfo]) -> Self

Build a suppression context from parsed modules.

pub fn is_suppressed(&self, file_id: FileId, line: u32, kind: IssueKind) -> bool

Check if a specific issue at a given line should be suppressed, and mark the matching suppression as consumed.

pub fn is_file_suppressed(&self, file_id: FileId, kind: IssueKind) -> bool

Check if the entire file is suppressed for the given kind, and mark the matching suppression as consumed.

pub fn is_policy_suppressed( &self, file_id: FileId, line: u32, pack: &str, rule_id: &str, ) -> bool

Check if a policy finding at a given line should be suppressed.

pub fn get(&self, file_id: FileId) -> Option<&[Suppression]>

Get the raw suppressions for a file (for detectors that need direct access).

pub fn used_count(&self) -> usize

Count suppression entries that matched at least one issue.

pub fn find_stale( &self, graph: &ModuleGraph, config: &ResolvedConfig, ) -> Vec<StaleSuppression>

Collect all suppressions that were never consumed by any detector.

Skips suppression kinds that are checked in the CLI layer (complexity, coverage gaps, feature flags, code duplication) to avoid false positives. Also skips suppressions whose target kind is disabled (Severity::Off) under the resolved rules for the suppression’s file, including per-file overrides.rules: the detector never ran, so the suppression appears unconsumed, but is not actually stale (it documents intentional dormancy and becomes valid again the moment the rule is re-enabled). See issue #482.

pub fn find_missing_reasons(&self, graph: &ModuleGraph) -> Vec<StaleSuppression>

Collect suppression comments that are missing -- <reason>.

pub fn all_suppressions(&self, graph: &ModuleGraph) -> Vec<ActiveSuppression>

Collect every suppression comment present in the analyzed files this run, keyed by file path and kind.

This is the “active-suppression state” the Fallow Impact value report needs (issue: v1.5 attribution): to tell a genuinely resolved finding (code removed) from one merely silenced by a newly-added fallow-ignore, impact records which suppressions are in play each run and looks for ones that newly appeared covering a disappeared finding’s kind.

Unlike Self::find_stale, this returns ALL present suppressions regardless of whether a core detector consumed them, and across every kind (dead-code, complexity, code-duplication, …). Impact only needs to know a suppression for (file, kind) exists; a present-but-stale entry is harmless because impact’s discriminator keys on a suppression that newly appeared between two recorded runs, and a finding silenced by a present suppression was never reported (so it never enters the resolved tally). Complexity and code-duplication suppressions are consumed in the CLI layer rather than through this context, so capturing presence here is the single uniform mechanism that covers all three impact categories.