Trait implementation for both a trait object and for direct implementors of the trait

by

Implement your trait for all Box<S> where S implements your trait. Then you can delegate to the existing implementation:

impl<S: Solid + ?Sized> Solid for Box<S> {
    fn intersect(&self, ray: f32) -> f32 {
        (**self).intersect(ray)
        // Some people prefer this less-ambiguous form
        // S::intersect(self, ray)
    }
}

You’ll also find that it can be useful to do the same for references:

impl<S: Solid + ?Sized> Solid for &'_ S {
    fn intersect(&self, ray: f32) -> f32 {
        (**self).intersect(ray)
        // Some people prefer this less-ambiguous form
        // S::intersect(self, ray)
    }
}

All together:

trait Solid {
    fn intersect(&self, ray: f32) -> f32;
}

impl<S: Solid + ?Sized> Solid for Box<S> {
    fn intersect(&self, ray: f32) -> f32 {
        (**self).intersect(ray)
        // S::intersect(self, ray)
    }
}

impl<S: Solid + ?Sized> Solid for &'_ S {
    fn intersect(&self, ray: f32) -> f32 {
        (**self).intersect(ray)
        // S::intersect(self, ray)
    }
}

struct Group<S>(Vec<S>);

impl<S: Solid> Solid for Group<S> {
    fn intersect(&self, _ray: f32) -> f32 {
        42.42
    }
}

struct Point;

impl Solid for Point {
    fn intersect(&self, _ray: f32) -> f32 {
        100.
    }
}

fn main() {
    let direct = Group(vec![Point]);
    let boxed = Group(vec![Box::new(Point)]);
    let pt = Point;
    let reference = Group(vec![&pt]);

    let mixed: Group<Box<dyn Solid>> = Group(vec![
        Box::new(direct),
        Box::new(boxed),
        Box::new(Point),
        Box::new(reference),
    ]);

    mixed.intersect(1.0);
}

The ?Sized bound allows the S to not have a size known at compile time. Importantly, this allows you to pass in trait objects such as Box<dyn Solid> or &dyn Solid as the type Solid does not have a known size.

See also:

More Related Contents:

  1. Traits and Rust
  2. How to get a reference to a concrete type from a trait object?
  3. Why can impl trait not be used to return multiple / conditional types?
  4. How do I implement a trait I don’t own for a type I don’t own?
  5. What makes something a “trait object”?
  6. Is it possible to use `impl Trait` as a function’s return type in a trait definition?
  7. How do I return an instance of a trait from a method?
  8. I implemented a trait for another trait but cannot call methods from both traits
  9. Why would I implement methods on a trait instead of as part of the trait?
  10. How does the mechanism behind the creation of boxed traits work?
  11. Why is the `Sized` bound necessary in this trait?
  12. How can I implement Rust’s Copy trait?
  13. Is there any trait that specifies numeric functionality?
  14. Understanding Traits and Object Safety
  15. How do I pass a closure through raw pointers as an argument to a C function?
  16. Can’t implement a trait I don’t own for all types that implement a trait I do own
  17. How do I specify that a struct field must implement a trait?
  18. Rust equivalent to Swift’s extension methods to a protocol?
  19. Cannot use moved BufReader after for loop with bufreader.lines()
  20. Do I have to implement a trait twice when implementing it for both reference and non-reference types?
  21. Why can’t I store a value and a reference to that value in the same struct?
  22. Why does Iterator::take_while take ownership of the iterator?
  23. How do I read the entire body of a Tokio-based Hyper request?
  24. How does Rust pattern matching determine if the bound variable will be a reference or a value?
  25. print! macro not executed until pressing Enter
  26. Can traits be used on enum types?
  27. Implement fmt::Display for Vec
  28. Why does the Rust compiler request I constrain a generic type parameter’s lifetime (error E0309)?
  29. Cannot pass self as callback parameter due to double borrowing
  30. How do I create a HashMap with type erased keys?

Leave a Comment