rmc-type-overlaps

Audit a Rust workspace for type overlaps to detect cross-crate type collisions and module shadowing. This identifies duplicate definitions and ambiguous types, reducing migration debt and preventing incorrect symbol resolution during codebase refactoring.

Module shadowing in Rust occurs when a module or type name obscures another, changing what references resolve to. It becomes problematic during structural audits or refactoring when duplicate definitions silently accumulate, creating migration debt and ambiguous symbol resolution across the workspace.

Perform a single-crate hygiene audit by narrowing overlap findings to one crate using the crate’s module tree and overlap filtering. This guides investigation into within-crate duplicate type names and overly common function names indicating missing abstractions.

Verify Rust naming collision severity by analyzing consumer-usage patterns with semantic similarity checks. Use who-uses summaries and find_definition to rank severity and recommend remediation actions like renaming modules, merging duplicates, or factoring test fixtures.

Yes, semantic similarity checks help identify overly common Rust function names that may indicate missing abstractions. During a structural audit, these checks rank severity and recommend actions like factoring test fixtures or merging duplicate definitions to improve structural hygiene.

Run a workspace-wide overlap audit to reduce migration debt in an unfamiliar Rust codebase. Detecting cross-crate type collisions and module shadowing early prevents incorrect symbol resolution and guides structural hygiene remediation during onboarding.