Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
actionbook avatar

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)
At a glance

m04-zero-cost capabilities & compatibility

Capabilities
polymorphism strategy selection · trait bound error interpretation · object safety evaluation · performance trade off routing
From the docs

What m04-zero-cost says it does

Do we need compile-time or runtime polymorphism?
SKILL.md
E0277 | "Add trait bound" | Is this abstraction at the right level?
SKILL.md
npx skills add https://github.com/actionbook/rust-skills --skill m04-zero-cost

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.5k
repo stars1.3k
Security audit3 / 3 scanners passed
Last updatedMay 24, 2026
Repositoryactionbook/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

SKILL.mdMarkdownGitHub ↗

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

ErrorDon't Just SayAsk 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 ErrorTrace ToQuestion
Complex trait boundsm09-domainIs the abstraction right?
Object safety issuesm05-type-drivenCan typestate help?
Type explosionm10-performanceAccept 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

PatternDispatchCode SizeRuntime Cost
fn foo<T: Trait>()Static+bloatZero
fn foo(x: &dyn Trait)DynamicMinimalvtable lookup
impl Trait returnStatic+bloatZero
Box<dyn Trait>DynamicMinimalAllocation + 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>) { }  // owned

Error Code Reference

ErrorCauseQuick Fix
E0277Type doesn't impl traitAdd impl or change bound
E0308Type mismatchCheck generic params
E0599No method foundImport trait with use
E0038Trait not object-safeUse generics or redesign

---

Decision Guide

ScenarioChooseWhy
Performance criticalGenericsZero runtime cost
Heterogeneous collectiondyn TraitDifferent types at runtime
Plugin architecturedyn TraitUnknown types at compile
Reduce compile timedyn TraitLess monomorphization
Small, known type setenumNo indirection

---

Object Safety

A trait is object-safe if it:

  • Doesn't have Self: Sized bound
  • Doesn't return Self
  • Doesn't have generic methods
  • Uses where Self: Sized for non-object-safe methods

---

Anti-Patterns

Anti-PatternWhy BadBetter
Over-generic everythingCompile time, complexityConcrete types when possible
dyn for known typesUnnecessary indirectionGenerics
Complex trait hierarchiesHard to understandSimpler design
Ignore object safetyLimits flexibilityPlan for dyn if needed

---

Related Skills

WhenSee
Type-driven designm05-type-driven
Domain abstractionm09-domain
Performance concernsm10-performance
Send/Sync boundsm07-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.

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.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.