Enum rustc_middle::mir::interpret::CheckInAllocMsg

pub enum CheckInAllocMsg {
    MemoryAccessTest,
    PointerArithmeticTest,
    InboundsTest,
}

Details of why a pointer had to be in-bounds.

Variants

MemoryAccessTest

We are access memory.

PointerArithmeticTest

We are doing pointer arithmetic.

InboundsTest

None of the above – generic/unspecific inbounds test.

Trait Implementations

impl Clone for CheckInAllocMsg

fn clone(&self) -> CheckInAllocMsg

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CheckInAllocMsg

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'tcx, __D: TyDecoder<'tcx>> Decodable<__D> for CheckInAllocMsg

fn decode(__decoder: &mut __D) -> Result<Self, <__D as Decoder>::Error>

impl Display for CheckInAllocMsg

fn fmt(&self, f: &mut Formatter<'_>) -> Result

When this is printed as an error the context looks like this “{msg}pointer must be in-bounds at offset…”

impl<'tcx, __E: TyEncoder<'tcx>> Encodable<__E> for CheckInAllocMsg

fn encode(&self, __encoder: &mut __E) -> Result<(), <__E as Encoder>::Error>

impl<'__ctx> HashStable<StableHashingContext<'__ctx>> for CheckInAllocMsg

fn hash_stable(
    &self,
    __hcx: &mut StableHashingContext<'__ctx>,
    __hasher: &mut StableHasher
)

impl Copy for CheckInAllocMsg

Layout

Note: Most layout information is completely unstable and may be different between compiler versions and platforms. The only exception is types with certain repr(...) attributes. Please see the Rust Reference’s “Type Layout” chapter for details on type layout guarantees.

Size: 1 byte