rmc-enum-variants

Detecting unused Rust enum variants involves extracting variants from target enums and computing per-variant fan-in across the codebase. This reveals which variants lack construction sites or match patterns, flagging them as unused states.

Auditing enum variants for refactoring candidates requires listing variants with qualified names and measuring their usage load. By identifying all construction sites and pattern uses, you can isolate load-bearing states from redundant ones suitable for refactoring.

Finding convergent enum designs in Rust uses semantic overlaps to cluster identical variant models across different enums. This convergence detection spots duplicated state representations, helping you consolidate overlapping enum structures during code auditing.

Enum variant usage analysis works with non_exhaustive attributes by applying attribute-aware dead-state checks. This ensures that unused findings are interpreted correctly, preventing false positives when variants are marked to allow future additions outside the current crate.

To start analyzing Rust enum variants using static analysis, build the hypergraph and index the codebase. Then run the enum variant extraction step for your target enum, followed by querying who uses each variant to see which states carry usage.

You can measure enum variant fan-in across a Rust workspace by indexing the codebase and querying per-variant usage. This identifies all construction sites and match patterns, quantifying how often each variant is referenced within the workspace call graph.