commit | 46697198d609f156775a0863bbd449e3ec84be67 | [log] [tgz] |
---|---|---|
author | Martin Geisler <[email protected]> | Wed Nov 15 16:47:11 2023 +0100 |
committer | Martin Geisler <[email protected]> | Mon Dec 11 10:22:10 2023 +0000 |
tree | ff176214b85e9271e57b726f443643ddc3042b27 | |
parent | 21be4635b1b8eabdf7a3abed6367ada2e24be5c6 [diff] |
Import 'downcast' crate Request Document: go/android-rust-importing-crates For CL Reviewers: go/android3p#cl-review For Build Team: go/ab-third-party-imports Bug: http://b/310600230 Change-Id: I68fb2495b218f6b930072e2ee052402036c3d56e IGNORE_COMPLIANCELINT=LicenseIsKnown: I believe the symlink is triggering b/270248598
A trait (& utilities) for downcasting trait objects back to their original types.
Add to your Cargo.toml:
[dependencies] downcast = "0.12"
Add to your crate root:
#[macro_use] extern crate downcast;
Arc
-pointers.Downcast::downcast()
).Any::type_name()
).Q: I'm getting the size for values of type XXX cannot be known at compile time
errors, what am i doing wrong?
A: Make sure you use the corresponding Any
bound along with the Downcast
traits. So, Any
for Downcast
and AnySync
for DowncastSync
.
Q: Can i cast trait objects to trait objects?
A: No, that is currently no possible in safe rust - and unsafe solutions are very tricky, as well. If you found a solution, feel free to share it!
Q: What is the difference between this and the downcast-rs
crate on crates.io?
A: At the moment, there isn't one, really. There was an unfortunate naming clash. You may consider using the other crate, as it is more actively maintained. This one is considered feature-complete and frozen in functionality. Hopefully, one day, the Rust language will make downcasting easier and we will need neither of these crates anymore!