#type #layout #derive #type-layout #1 #foo

macro type-layout-derive

Derive macro implementation for type-layout crate

2 unstable releases

0.2.0 Sep 19, 2020
0.1.0 Sep 13, 2020
Download history 5406/week @ 2023-10-30 5055/week @ 2023-11-06 4802/week @ 2023-11-13 3093/week @ 2023-11-20 5325/week @ 2023-11-27 6645/week @ 2023-12-04 6122/week @ 2023-12-11 6423/week @ 2023-12-18 2566/week @ 2023-12-25 5061/week @ 2024-01-01 7097/week @ 2024-01-08 6800/week @ 2024-01-15 8386/week @ 2024-01-22 9352/week @ 2024-01-29 8214/week @ 2024-02-05 8493/week @ 2024-02-12

34,686 downloads per month
Used in 7 crates (via type-layout)

MIT/Apache

6KB
73 lines

type-layout

GitHub CI Status type-layout on crates.io type-layout docs

type-layout is a type layout debugging aid, providing a #[derive]able trait that reports:

  • The type's name, size, and minimum alignment
  • Each field's name, type, offset, and size
  • Padding due to alignment requirements

type-layout currently only functions on structs with named fields. This is a temporary limitation.

Examples

The layout of types is only defined if they're #[repr(C)]. This crate works on non-#[repr(C)] types, but their layout is unpredictable.

use type_layout::TypeLayout;

#[derive(TypeLayout)]
#[repr(C)]
struct Foo {
    a: u8,
    b: u32,
}

println!("{}", Foo::type_layout());
// prints:
// Foo (size 8, alignment 4)
// | Offset | Name      | Size |
// | ------ | --------- | ---- |
// | 0      | a         | 1    |
// | 1      | [padding] | 3    |
// | 4      | b         | 4    |

Over-aligned types have trailing padding, which can be a source of bugs in some FFI scenarios:

use type_layout::TypeLayout;

#[derive(TypeLayout)]
#[repr(C, align(128))]
struct OverAligned {
    value: u8,
}

println!("{}", OverAligned::type_layout());
// prints:
// OverAligned (size 128, alignment 128)
// | Offset | Name      | Size |
// | ------ | --------- | ---- |
// | 0      | value     | 1    |
// | 1      | [padding] | 127  |

Minimum Supported Rust Version (MSRV)

type-layout supports Rust 1.34.1 and newer. Until type-layout reaches 1.0, changes to the MSRV will require major version bumps. After 1.0, MSRV changes will only require minor version bumps, but will need significant justification.

License

Licensed under either of

at your option.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.

Dependencies

~1.5MB
~32K SLoC