snippetrustCritical
How to get a reference to a concrete type from a trait object?
Viewed 0 times
objecthowfromconcretetypereferencetraitget
Problem
How do I get
This code returns an error:
Box or &B or &Box from the a variable in this code:trait A {}
struct B;
impl A for B {}
fn main() {
let mut a: Box = Box::new(B);
let b = a as Box;
}This code returns an error:
error[E0605]: non-primitive cast: std::boxed::Box as std::boxed::Box
--> src/main.rs:8:13
|
8 | let b = a as Box;
| ^^^^^^^^^^^
|
= note: an as expression can only be used to convert between primitive types. Consider using the From trait
Solution
There are two ways to do downcasting in Rust. The first is to use
The other way is to implement a method for each "target" on the base trait (in this case,
Wait, why do we need
Even if you add
But there's an implementation of
That is what
Note that you can side-step this whole problem by just not using
However, this precludes you from having any other methods; all you can do here is downcast to a concrete type.
As a final note of potential interest, the mopa crate allows you to combine the functionality of
Any. Note that this only allows you to downcast to the exact, original concrete type. Like so:use std::any::Any;
trait A {
fn as_any(&self) -> &dyn Any;
}
struct B;
impl A for B {
fn as_any(&self) -> &dyn Any {
self
}
}
fn main() {
let a: Box = Box::new(B);
// The indirection through `as_any` is because using `downcast_ref`
// on `Box` *directly* only lets us downcast back to `&A` again.
// The method ensures we get an `Any` vtable that lets us downcast
// back to the original, concrete type.
let b: &B = match a.as_any().downcast_ref::() {
Some(b) => b,
None => panic!("&a isn't a B!"),
};
}The other way is to implement a method for each "target" on the base trait (in this case,
A), and implement the casts for each desired target type.Wait, why do we need
as_any?Even if you add
Any as a requirement for A, it's still not going to work correctly. The first problem is that the A in Box will also implement Any... meaning that when you call downcast_ref, you'll actually be calling it on the object type A. Any can only downcast to the type it was invoked on, which in this case is A, so you'll only be able to cast back down to &dyn A which you already had.But there's an implementation of
Any for the underlying type in there somewhere, right? Well, yes, but you can't get at it. Rust doesn't allow you to "cross cast" from &dyn A to &dyn Any.That is what
as_any is for; because it's something only implemented on our "concrete" types, the compiler doesn't get confused as to which one it's supposed to invoke. Calling it on an &dyn A causes it to dynamically dispatch to the concrete implementation (again, in this case, B::as_any), which returns an &dyn Any using the implementation of Any for B, which is what we want.Note that you can side-step this whole problem by just not using
A at all. Specifically, the following will also work:fn main() {
let a: Box = Box::new(B);
let _: &B = match a.downcast_ref::() {
Some(b) => b,
None => panic!("&a isn't a B!")
};
}However, this precludes you from having any other methods; all you can do here is downcast to a concrete type.
As a final note of potential interest, the mopa crate allows you to combine the functionality of
Any with a trait of your own.Code Snippets
use std::any::Any;
trait A {
fn as_any(&self) -> &dyn Any;
}
struct B;
impl A for B {
fn as_any(&self) -> &dyn Any {
self
}
}
fn main() {
let a: Box<dyn A> = Box::new(B);
// The indirection through `as_any` is because using `downcast_ref`
// on `Box<A>` *directly* only lets us downcast back to `&A` again.
// The method ensures we get an `Any` vtable that lets us downcast
// back to the original, concrete type.
let b: &B = match a.as_any().downcast_ref::<B>() {
Some(b) => b,
None => panic!("&a isn't a B!"),
};
}fn main() {
let a: Box<dyn Any> = Box::new(B);
let _: &B = match a.downcast_ref::<B>() {
Some(b) => b,
None => panic!("&a isn't a B!")
};
}Context
Stack Overflow Q#33687447, score: 161
Revisions (0)
No revisions yet.