M04 Zero Cost

作者 actionbook5c40d3ad7851无许可证1.5K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库6周前更新

CRITICAL: Use for generics, traits, zero-cost abstraction. Triggers: E0277, E0308, E0599, generic, trait, impl, dyn, where, monomorphization, static dispatch, dynamic dispatch, impl Trait, trait bound not satisfied, 泛型, 特征, 零成本抽象, 单态化

AI 生成的概览

指导 Rust 开发者选择泛型、trait 对象与零成本抽象,并解决相关编译错误。

功能
该技能为 Rust 多态提供决策指导:何时使用泛型或 impl Trait 实现静态分发,何时使用 dyn Trait 或 Box 实现动态分发。它把 E0277、E0308、E0599、E0038 等常见编译错误映射为设计问题,并提供关于分发开销、语法对比、对象安全与反模式的速查表。它产出的是推理与建议,而非代码文件。
适用场景
适用于处理 Rust 泛型、trait 约束、impl Trait、dyn Trait 或单态化,或遇到与 trait 相关的编译错误时。在需要权衡编译期与运行期多态,或设计类型抽象时也很有用。
运行要求
无需任何工具、软件包或凭据;仅为说明性内容,不附带脚本。

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

rust
// Static dispatch - type known at compile timefn process(x: impl Display) { }      // argument positionfn process<T: Display>(x: T) { }     // explicit genericfn get() -> impl Display { }         // return position
// Dynamic dispatch - type determined at runtimefn process(x: &dyn Display) { }      // referencefn 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

来源与署名

来源:actionbook/rust-skills位于skills/m04-zero-cost提交5c40d3a

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架