commit | cab10406ac0bf318dbe127f268adcce517e8ac83 | [log] [tgz] |
---|---|---|
author | James Farrell <[email protected]> | Tue Dec 03 20:38:28 2024 +0000 |
committer | Automerger Merge Worker <[email protected]> | Tue Dec 03 20:38:28 2024 +0000 |
tree | a72f02da0693ae0df2205e775b8e7d715f3ce94c | |
parent | fabd8fb43539cd036fd9001eaa670acabbd3a7a6 [diff] | |
parent | 84f95448f7e339b0c93553918647e922869556d5 [diff] |
Migrate 9 newly imported crates to monorepo am: 4dc2762c1a am: 84f95448f7 Original change: https://android-review.googlesource.com/c/platform/external/rust/crates/ptr_meta/+/3390019 Change-Id: Ib07e812d64a1261d9a491c841d16f382beb518db Signed-off-by: Automerger Merge Worker <[email protected]>
A radioactive stabilization of the ptr_meta
RFC.
Sized types already have Pointee
implemented for them, so most of the time you won't have to worry about them. However, trying to derive Pointee
for a struct that may or may not have a DST as its last field will cause an implementation conflict with the automatic sized implementation.
slice
s and str
sThese core types have implementations built in.
You can derive Pointee
for last-field DSTs:
use ptr_meta::Pointee; #[derive(Pointee)] struct Block<H, T> { header: H, elements: [T], }
You can generate a Pointee
for trait objects:
use ptr_meta::pointee; // Generates Pointee for dyn Stringy #[pointee] trait Stringy { fn as_string(&self) -> String; }