| commit | c32c63e6c845861da532df639ae33a27d8e35ee2 | [log] [tgz] |
|---|---|---|
| author | Android Build Coastguard Worker <[email protected]> | Wed Dec 04 00:09:23 2024 +0000 |
| committer | Android Build Coastguard Worker <[email protected]> | Wed Dec 04 00:09:23 2024 +0000 |
| tree | a72f02da0693ae0df2205e775b8e7d715f3ce94c | |
| parent | 8cedf65b8263f7addcb996b062a6cac59e1f411c [diff] | |
| parent | 4dc2762c1a9f14b15a4a90bf1eecb3c06b4d6756 [diff] |
Snap for 12743396 from 4dc2762c1a9f14b15a4a90bf1eecb3c06b4d6756 to sdk-release Change-Id: Iafc05a3b6fd9df6c1732f206e79162b004c5b165
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.
slices and strsThese 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; }