m04-zero-cost

Static dispatch uses generics for compile-time monomorphization and zero-cost abstraction, while dynamic dispatch uses trait objects for runtime flexibility but adds a small performance overhead.

Rust trait object safety errors occur when a trait contains generic methods or returns Self, preventing the compiler from creating a vtable. You must modify the trait definition or switch to static dispatch using generics to resolve this issue.

Fixing Rust trait bound errors involves adding the required trait constraints to your generic type parameters. The compiler indicates missing bounds needed for specific method calls, allowing proper static dispatch and type safety.

Use trait objects in Rust when you need runtime polymorphism, heterogeneous collections, or reduced binary size. Use generics when you need maximum performance, compile-time type checking, and static dispatch without vtable overhead.

Yes, using enums instead of trait objects is a viable Rust pattern for dynamic dispatch. Enums offer compile-time exhaustiveness checking and avoid vtable overhead, making them efficient for a known, closed set of types.

Dynamic dispatch in Rust limits you to object-safe traits, prevents generic method usage, and introduces runtime vtable overhead. Additionally, trait objects require heap allocation via Box or references, restricting ownership flexibility.