Passing &Box<T> as &T

Understanding deref coercion with Box types in Rust

This is a medium-difficulty Rust language-knowledge question that tests your grasp of deref coercion, one of Rust's most practical but subtle features. It appears frequently in technical interviews because it separates candidates who have merely used Rust from those who understand its type system deeply.

The question asks you to explain why the type system permits a reference to a boxed value to be passed where a reference to the unboxed value is expected. Working through this requires understanding the interaction between trait implementations, automatic type conversions, and how Rust's borrow checker applies implicit transformations at call sites. The answer hinges on a specific trait that Box implements, along with how Rust applies its deref coercion rules.

• The Deref trait and deref coercion rules
• Trait implementations for standard library types
• Implicit vs. explicit type conversions in function calls
• Ownership and borrowing semantics