m04-zero-cost

Choose generics for static dispatch and maximum performance when type sets are known at compile time, and trait objects for dynamic dispatch when flexibility across varying types is required. This guidance optimizes library design by balancing monomorphization trade-offs against runtime flexibility.

Monomorphization generates specialized code for each generic type at compile time, enabling static dispatch and zero-cost abstractions while increasing binary size. This Skill analyzes your API scenarios to guide when these compile-time trade-offs benefit performance-critical code paths.

impl Trait uses static dispatch for zero-cost abstractions via compile-time monomorphization, whereas dyn Trait uses dynamic dispatch allowing runtime polymorphism. This Skill guides the selection between them based on your library API stability and performance requirements.

Object safety determines whether a trait can be used as a dyn Trait object for dynamic dispatch. This Skill provides practical guidelines for addressing object safety requirements and selecting between generics or trait objects in your Rust library design.

Yes, by analyzing usage patterns across modules to select generics for static dispatch or trait objects for dynamic dispatch. This Skill evaluates scenarios with varying type sets to maintain zero-cost abstractions and optimize performance-critical code paths.

Generics cause monomorphization, duplicating code for each type to achieve zero-cost static dispatch. This Skill analyzes your Rust API to guide trade-offs between monomorphization binary bloat and dynamic dispatch flexibility for performance optimization.