为何无法将实现扩展trait的Box转换为实现基trait的Box？

Great question! Let's break down why this conversion fails and how to fix it.

First, the core issue: even though Derived is a subtrait of Base, Box<dyn Derived> and Box<dyn Base> are distinct types in Rust. Unlike some OOP languages where upcasting happens automatically, Rust doesn't implicitly convert between these trait objects because their underlying virtual tables (vtables) have different structures.

A Box<dyn Derived> holds a fat pointer: one pointing to your Foo instance, and another pointing to a vtable that includes all methods from both Base and Derived. In contrast, Box<dyn Base> expects a vtable that only contains methods defined in Base. Rust won't automatically slice the Derived vtable to fit Base's requirements—you need to explicitly tell the compiler to perform this conversion.

Fixing the code #

You can use the as keyword to explicitly cast the Box<dyn Derived> to Box<dyn Base>:

trait Base { }
trait Derived : Base { }
struct Foo { }
impl Base for Foo { }
impl Derived for Foo { }
fn main() {
    let b: Box<dyn Derived> = Box::new(Foo {});
    let a: Box<dyn Base> = b as Box<dyn Base>; // Explicit cast here
}

This works because the compiler recognizes that Derived extends Base, so it can safely create a new Box<dyn Base> using the data pointer from the original box and a trimmed vtable that only includes Base methods.

Why no implicit conversion? #

Rust prioritizes safety and explicitness. Implicit upcasting of trait objects could lead to unexpected behavior in more complex scenarios (like when traits have associated types or conflicting method signatures). By requiring an explicit cast, Rust makes your intent clear and avoids silent type changes that might introduce hard-to-track bugs.

内容的提问来源于stack exchange，提问作者bofjas