Struct SpecificityScorer 

pub struct SpecificityScorer { /* private fields */ }

Scores module names based on specificity and descriptiveness

Implementations

impl SpecificityScorer

pub fn new() -> Self

Create a new specificity scorer with default configuration

pub fn calculate_specificity(&self, name: &str) -> f64

Calculate specificity score for a module name

Returns a score from 0.0 (completely generic) to 1.0 (highly specific).

Arguments

• name - Module name to score (without .rs extension)

Returns

Specificity score in range [0.0, 1.0]

pub fn is_acceptable(&self, name: &str, min_threshold: f64) -> bool

Check if a name is acceptable (above minimum threshold)

Arguments

• name - Module name to check
• min_threshold - Minimum acceptable specificity (default: 0.4)

Returns

true if name meets minimum specificity, false otherwise

pub fn assess_quality(&self, name: &str) -> &'static str

Get a human-readable assessment of name quality

pub fn calculate_specificity_type_aware( &self, name: &str, is_type_based: bool, ) -> f64

Calculate specificity score with type-awareness (Spec 193 Phase 2)

Type-based splits get stricter penalties for generic names because they originate from Rust type names which are often too vague for module names.

Arguments

• name - Module name to score (without .rs extension)
• is_type_based - true if this name comes from type-based clustering

Returns

Specificity score in range [0.0, 1.0]

pub fn is_acceptable_for_type_based(&self, name: &str) -> bool

Check if name is acceptable for type-based splits (stricter threshold)

Type-based splits require a higher quality bar (0.65) because they originate from type names which are often too generic.

Trait Implementations

impl Default for SpecificityScorer

fn default() -> Self

Returns the “default value” for a type.