Trait objects overview in Rust

Introduction

Trait objects let you use different types in the same place if they share some behavior. This helps write flexible and reusable code.

When you want to store different types that implement the same trait in one collection.

When you want to write functions that accept any type with certain behavior without knowing the exact type.

When you want to call methods on types dynamically at runtime instead of compile time.

When you need to hide the concrete type details but keep the ability to use trait methods.

Syntax

Rust

let obj: &dyn TraitName = &value;
let boxed_obj: Box<dyn TraitName> = Box::new(value);

dyn TraitName means a trait object for the trait TraitName.

You can use references &dyn TraitName or smart pointers like Box<dyn TraitName>.

Examples

Use a reference to a trait object to call a method on a value of unknown concrete type but known behavior.

Rust

trait Speak {
    fn speak(&self);
}

struct Dog;
impl Speak for Dog {
    fn speak(&self) {
        println!("Woof!");
    }
}

fn main() {
    let dog = Dog;
    let speaker: &dyn Speak = &dog;
    speaker.speak();
}

Store different drawable shapes in a vector using boxed trait objects.

Rust

trait Draw {
    fn draw(&self);
}

struct Circle;
impl Draw for Circle {
    fn draw(&self) {
        println!("Drawing a circle");
    }
}

fn main() {
    let shapes: Vec<Box<dyn Draw>> = vec![Box::new(Circle)];
    for shape in shapes {
        shape.draw();
    }
}

Sample Program

This program shows how to use trait objects to call the same method on different types that implement the Animal trait.

Rust

trait Animal {
    fn sound(&self);
}

struct Cat;
impl Animal for Cat {
    fn sound(&self) {
        println!("Meow");
    }
}

struct Dog;
impl Animal for Dog {
    fn sound(&self) {
        println!("Woof");
    }
}

fn make_sound(animal: &dyn Animal) {
    animal.sound();
}

fn main() {
    let cat = Cat;
    let dog = Dog;

    let animals: Vec<&dyn Animal> = vec![&cat, &dog];

    for animal in animals {
        make_sound(animal);
    }
}

Important Notes

Trait objects use dynamic dispatch, which means the method to call is decided at runtime.

You cannot use trait objects with traits that have generic methods or associated constants.

Use dyn keyword to clearly mark trait objects since Rust 2018 edition.

Summary

Trait objects let you work with different types through a common interface.

They enable dynamic dispatch to call methods at runtime.

Use references or smart pointers with dyn Trait to create trait objects.

Practice

1. What is the main purpose of using trait objects in Rust?

easy

A. To allow different types to be used through a common interface at runtime

B. To improve compile-time performance by avoiding dynamic dispatch

C. To create new data types that do not implement any traits

D. To statically bind methods to specific types only

Solution

1. Step 1: Understand trait objects concept

   Trait objects let you use different types that implement the same trait through a common interface.

2. Step 2: Identify dynamic dispatch role

   Trait objects enable dynamic dispatch, meaning method calls are decided at runtime, allowing flexibility.

3. Final Answer:

   To allow different types to be used through a common interface at runtime -> Option A

4. Quick Check:

   Trait objects = common interface + runtime dispatch [OK]

Hint: Trait objects enable runtime method calls on different types [OK]

Common Mistakes:

• Confusing trait objects with static dispatch
• Thinking trait objects create new unrelated types
• Believing trait objects improve compile-time speed

2. Which of the following is the correct syntax to create a trait object reference for a trait named Animal?

easy

A. let a: &Animal = &dog;

B. let a: Animal = &dog;

C. let a: dyn Animal = dog;

D. let a: &dyn Animal = &dog;

Solution

1. Step 1: Recall trait object syntax

   Trait objects require the dyn keyword before the trait name when used as a reference or pointer.

2. Step 2: Check each option

   let a: &dyn Animal = &dog; uses &dyn Animal, which is the correct syntax for a trait object reference.

3. Final Answer:

   let a: &dyn Animal = &dog; -> Option D

4. Quick Check:

   Trait object syntax = &dyn Trait [OK]

Hint: Use &dyn Trait for trait object references [OK]

Common Mistakes:

• Omitting the dyn keyword
• Trying to use trait name without reference
• Assigning trait object without pointer or reference

3. What will be the output of the following Rust code?

trait Speak {
    fn speak(&self) -> String;
}

struct Dog;
impl Speak for Dog {
    fn speak(&self) -> String {
        "Woof".to_string()
    }
}

struct Cat;
impl Speak for Cat {
    fn speak(&self) -> String {
        "Meow".to_string()
    }
}

fn animal_speak(animal: &dyn Speak) {
    println!("{}", animal.speak());
}

fn main() {
    let dog = Dog;
    let cat = Cat;
    animal_speak(&dog);
    animal_speak(&cat);
}

medium

A. Woof\nMeow

B. Dog\nCat

C. Woof\nWoof

D. Compilation error due to trait object usage

Solution

1. Step 1: Understand trait implementations

   Dog and Cat both implement the Speak trait with their own speak() returning "Woof" and "Meow" respectively.

2. Step 2: Analyze function calls with trait objects

   animal_speak takes a reference to a dyn Speak trait object and calls speak(), which uses dynamic dispatch to call the correct method.

3. Final Answer:

   Woof\nMeow -> Option A

4. Quick Check:

   Dynamic dispatch calls correct speak() = Woof then Meow [OK]

Hint: Trait objects call correct method at runtime [OK]

Common Mistakes:

• Expecting static dispatch output
• Confusing struct names with method output
• Thinking code causes compilation error

4. Identify the error in the following Rust code using trait objects:

trait Draw {
    fn draw(&self);
}

struct Circle;
impl Draw for Circle {
    fn draw(&self) {
        println!("Drawing Circle");
    }
}

fn main() {
    let c = Circle;
    let obj: Box<Draw> = Box::new(c);
    obj.draw();
}

medium

A. Circle does not implement Draw trait

B. Missing dyn keyword in Box type declaration

C. Cannot call draw() on Box pointer

D. Box::new() requires a reference, not value

Solution

1. Step 1: Check trait object syntax in Box

   Trait objects require the dyn keyword when used as a pointer type like Box.

2. Step 2: Identify missing dyn keyword

   The code uses Box<Draw> instead of Box, causing a syntax error.

3. Final Answer:

   Missing dyn keyword in Box type declaration -> Option B

4. Quick Check:

   Box trait object needs dyn keyword [OK]

Hint: Always use dyn with trait objects in pointers like Box [OK]

Common Mistakes:

• Omitting dyn keyword in trait object types
• Assuming trait implementation is missing
• Thinking Box cannot call trait methods

5. You want to store different shapes (Circle, Square) in a single vector and call their area() method at runtime. Which approach correctly uses trait objects to achieve this?

trait Shape {
    fn area(&self) -> f64;
}

struct Circle { radius: f64 }
struct Square { side: f64 }

impl Shape for Circle {
    fn area(&self) -> f64 { 3.14 * self.radius * self.radius }
}

impl Shape for Square {
    fn area(&self) -> f64 { self.side * self.side }
}

fn main() {
    // Fill in the blank
    let shapes: Vec> = vec![
        Box::new(Circle { radius: 2.0 }),
        Box::new(Square { side: 3.0 }),
    ];

    for shape in shapes.iter() {
        println!("Area: {}", shape.area());
    }
}

hard

A. Use Vec<&Shape> with references to shapes without Box

B. Use Vec<Shape> directly without pointers

C. Use Vec> with Box::new for each shape

D. Use Vec without Box or references

Solution

1. Step 1: Understand trait object storage

   Trait objects must be stored behind pointers like Box or references because their size is unknown at compile time.

2. Step 2: Analyze vector type and initialization

   Using Vec> with Box::new() for each shape correctly stores different types implementing Shape.

3. Final Answer:

   Use Vec> with Box::new for each shape -> Option C

4. Quick Check:

   Trait objects need pointers like Box in collections [OK]

Hint: Store trait objects in Box pointers inside collections [OK]

Common Mistakes:

• Trying to store trait objects directly without pointers
• Using Vec<Shape> which is invalid
• Using references without ensuring lifetime