Decide between generics and trait objects for zero-cost abstraction in Rust.
npx skills add https://github.com/yumazak/kodo --skill m04-zero-cost-yumazak
Please help me install this Agent Skill. Skill: m04-zero-cost Source: https://github.com/yumazak/kodo/tree/main/.agents/skills/m04-zero-cost Command: npx skills add https://github.com/yumazak/kodo --skill m04-zero-cost-yumazak
Rust developers often face a tradeoff between zero-cost generics and dynamic dispatch via trait objects. This skill helps decide when to apply generics or trait objects to achieve zero-cost abstractions while preserving flexibility and safety.
Provide a recommended decision for a Rust function or type to use generics or trait objects and explain the expected performance and code-size impact.
High-intent search queries and answers about installing and using this skill.
Choose Rust generics for static dispatch when you know types at compile time to achieve zero-cost abstractions, and use trait objects for dynamic dispatch when runtime polymorphism is required for flexibility.
Monomorphization in Rust generates specific machine code for each generic type instantiation, maximizing runtime performance through static dispatch but increasing binary code size due to duplicated function implementations.
No, impl Trait in Rust primarily enables static dispatch at compile time. For dynamic dispatch, you must explicitly use dyn Trait to create trait objects and leverage runtime polymorphism.
Rust trait objects require the trait to be object-safe, meaning it cannot have methods returning Self or taking generic parameters, ensuring dynamic dispatch works correctly at runtime via vtables.
For a Rust library, use static dispatch with explicit trait bounds to maximize performance, or offer dynamic dispatch via trait objects to reduce compile times and binary size for diverse consumers.
Using generics causes longer Rust compile times because monomorphization forces the compiler to generate and optimize separate static dispatch code for every concrete type used, unlike dynamic dispatch.
adelabdelgawadDesign reusable Rust abstractions using traits, generics, and static dispatch.
jmdueaSelect Rust static or dynamic dispatch abstractions for code scenarios.
cecon123Guide Rust generics versus trait objects for zero-cost polymorphism decisions.
CallMeLuigiv2Evaluate Rust polymorphism decisions between generics and trait objects.
