
M04 Zero Cost
- 1.5k installs
- 1.3k repo stars
- Updated May 24, 2026
- actionbook/rust-skills
m04-zero-cost is an agent skill for Rust generics, traits, and static versus dynamic dispatch decisions.
About
The m04-zero-cost skill guides Rust generics, traits, and zero-cost abstraction decisions including errors E0277 E0308 E0599 E0038. Core question asks whether compile-time or runtime polymorphism is needed based on type knowledge at compile time, heterogeneous collections, and performance priority. Error mapping converts trait bound failures and object safety issues into abstraction level questions not blind bound additions. Thinking prompts choose trait versus enum versus concrete types and static impl Trait generics versus dynamic dyn Trait dispatch. Trace up links complex bounds to m09-domain and object safety to m05-type-driven. Use for generic, trait, impl, dyn, where, monomorphization, and trait bound not satisfied errors.
- Core question: compile-time or runtime polymorphism?
- Static dispatch: generics and impl Trait; runtime: dyn Trait.
- Errors E0277 E0308 E0599 E0038 mapped to design questions.
- Trait for same behavior different types; enum for different behavior same type.
- Trace up to m09-domain m05-type-driven m10-performance.
M04 Zero Cost by the numbers
- 1,463 all-time installs (skills.sh)
- +53 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #321 of 4,386 Backend & APIs skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
m04-zero-cost capabilities & compatibility
- Capabilities
- polymorphism strategy selection · trait bound error interpretation · object safety evaluation · performance trade off routing
What m04-zero-cost says it does
Do we need compile-time or runtime polymorphism?
E0277 | "Add trait bound" | Is this abstraction at the right level?
npx skills add https://github.com/actionbook/rust-skills --skill m04-zero-costAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.5k |
|---|---|
| repo stars | ★ 1.3k |
| Security audit | 3 / 3 scanners passed |
| Last updated | May 24, 2026 |
| Repository | actionbook/rust-skills ↗ |
Should I use generics, impl Trait, or dyn Trait for this Rust abstraction?
Choose Rust generics, traits, and static versus dynamic dispatch for zero-cost abstractions.
Who is it for?
Rust developers choosing trait bounds, generics, or trait objects.
Skip if: Skip for ownership errors in m01-ownership or smart pointers in m02-resource.
When should I use this skill?
User hits E0277 trait bound, generic trait impl dyn, or zero-cost abstraction questions.
What you get
A polymorphism choice matching compile-time type knowledge and performance requirements.
- Dispatch strategy decision
- Corrected trait/generic signatures
Files
Zero-Cost Abstraction
Layer 1: Language Mechanics
Core Question
Do we need compile-time or runtime polymorphism?
Before choosing between generics and trait objects:
- Is the type known at compile time?
- Is a heterogeneous collection needed?
- What's the performance priority?
---
Error → Design Question
| Error | Don't Just Say | Ask Instead |
|---|---|---|
| E0277 | "Add trait bound" | Is this abstraction at the right level? |
| E0308 | "Fix the type" | Should types be unified or distinct? |
| E0599 | "Import the trait" | Is the trait the right abstraction? |
| E0038 | "Make object-safe" | Do we really need dynamic dispatch? |
---
Thinking Prompt
Before adding trait bounds:
1. What abstraction is needed?
- Same behavior, different types → trait
- Different behavior, same type → enum
- No abstraction needed → concrete type
2. When is type known?
- Compile time → generics (static dispatch)
- Runtime → trait objects (dynamic dispatch)
3. What's the trade-off priority?
- Performance → generics
- Compile time → trait objects
- Flexibility → depends
---
Trace Up ↑
When type system fights back:
E0277 (trait bound not satisfied)
↑ Ask: Is the abstraction level correct?
↑ Check: m09-domain (what behavior is being abstracted?)
↑ Check: m05-type-driven (should use newtype?)| Persistent Error | Trace To | Question |
|---|---|---|
| Complex trait bounds | m09-domain | Is the abstraction right? |
| Object safety issues | m05-type-driven | Can typestate help? |
| Type explosion | m10-performance | Accept dyn overhead? |
---
Trace Down ↓
From design to implementation:
"Need to abstract over types with same behavior"
↓ Types known at compile time → impl Trait or generics
↓ Types determined at runtime → dyn Trait
"Need collection of different types"
↓ Closed set → enum
↓ Open set → Vec<Box<dyn Trait>>
"Need to return different types"
↓ Same type → impl Trait
↓ Different types → Box<dyn Trait>---
Quick Reference
| Pattern | Dispatch | Code Size | Runtime Cost |
|---|---|---|---|
fn foo<T: Trait>() | Static | +bloat | Zero |
fn foo(x: &dyn Trait) | Dynamic | Minimal | vtable lookup |
impl Trait return | Static | +bloat | Zero |
Box<dyn Trait> | Dynamic | Minimal | Allocation + vtable |
Syntax Comparison
// Static dispatch - type known at compile time
fn process(x: impl Display) { } // argument position
fn process<T: Display>(x: T) { } // explicit generic
fn get() -> impl Display { } // return position
// Dynamic dispatch - type determined at runtime
fn process(x: &dyn Display) { } // reference
fn process(x: Box<dyn Display>) { } // ownedError Code Reference
| Error | Cause | Quick Fix |
|---|---|---|
| E0277 | Type doesn't impl trait | Add impl or change bound |
| E0308 | Type mismatch | Check generic params |
| E0599 | No method found | Import trait with use |
| E0038 | Trait not object-safe | Use generics or redesign |
---
Decision Guide
| Scenario | Choose | Why |
|---|---|---|
| Performance critical | Generics | Zero runtime cost |
| Heterogeneous collection | dyn Trait | Different types at runtime |
| Plugin architecture | dyn Trait | Unknown types at compile |
| Reduce compile time | dyn Trait | Less monomorphization |
| Small, known type set | enum | No indirection |
---
Object Safety
A trait is object-safe if it:
- Doesn't have
Self: Sizedbound - Doesn't return
Self - Doesn't have generic methods
- Uses
where Self: Sizedfor non-object-safe methods
---
Anti-Patterns
| Anti-Pattern | Why Bad | Better |
|---|---|---|
| Over-generic everything | Compile time, complexity | Concrete types when possible |
dyn for known types | Unnecessary indirection | Generics |
| Complex trait hierarchies | Hard to understand | Simpler design |
| Ignore object safety | Limits flexibility | Plan for dyn if needed |
---
Related Skills
| When | See |
|---|---|
| Type-driven design | m05-type-driven |
| Domain abstraction | m09-domain |
| Performance concerns | m10-performance |
| Send/Sync bounds | m07-concurrency |
Related skills
Forks & variants (1)
M04 Zero Cost has 1 known copy in the catalog totaling 803 installs. They canonicalize to this original listing.
- zhanghandong - 803 installs
How it compares
Use m04-zero-cost for trait bound and dispatch architecture decisions rather than borrow checker or mutability-focused Rust skills.
FAQ
Generics or trait objects?
Generics when types are known at compile time; dyn Trait when types are determined at runtime.
Trait or enum abstraction?
Trait when different types share behavior; enum when one type has different behavioral variants.
Is m04-zero-cost safe to install?
Review the Security Audits panel on this page before installing in production.