Canonical associated type (as in New Type idiom)

One good way to represent types themselves as opposed to the values thereof is to use zero-sized types, which are commonly abbreviated as ZSTs. A programmer can have an enum whose variants store the corresponding [ZST] (and, implicitly, the [enum discriminant] that may or may not be optimized out); and then the size of the enum will not depend on the size of the types that are being represented.

At the time of writing, there is no canonical wrapper that would allow one to get [ZST] representing a type. The closest alternative is [core::marker::PhantomData][PhantomData], yet the semantics of [PhantomData] is [unnecessarily richer][PhantomData<*const T>] and has undesirable tradeoffs between generality/ease-of-use, for this, secondary use case.

Note: Even more precisely, the desired ZST<T> generic ZST is close to PhantomData<*const T>.

Since ZST<T> must represent T, it is natural to desire accessing the associated type. This crate offers TheAssocTyExt trait that is meant to be implemented for any type that has the associated type that is intended to be accessed.

Example

```rust use theassoctyext::TheAssocTyExt; use core::{ default::Default, mem::{sizeof, sizeofval}, marker::PhantomData };

[derive(Default)]

struct ZST(PhantomData<*const T>);

impl TheAssocTyExt for ZST { type TheAssocTy = T; }

// Repr is necessary to ensure the size of the discriminant

[repr(u8)]

enum PrimUnsignedIntKinds { U8(ZST), U16(ZST), U32(ZST), U64(ZST), U128(ZST), Usize(ZST), }

asserteq!(sizeof::>(), 0); asserteq!( sizeofval(&PrimUnsignedIntKinds::U16(ZST::::default())), sizeof::() ); asserteq!( sizeof::(), size_of::>() ); ```

Note: [core::mem::Discriminant][Discriminant], as the doc states, is [opaque]. Similarly, the data layout of any enum is rather vaguely specified for performance considerations. You can learn the deailts in [Unsafe Code Guidelines Reference].