pub fn mem_size(&self) -> Option<MemoryAccessSize> {
        if self.mem_size != 0 {
            Some(MemoryAccessSize { size: self.mem_size })
        } else {
            None
        }
    }
/// get the memory access information for this instruction, if it accesses memory.
///
/// the corresponding `MemoryAccessSize` may report that the size of accessed memory is
/// indeterminate; this is the case for `xsave/xrestor`-style instructions whose operation size
/// varies based on physical processor.
///
/// ## NOTE
///
/// the reported size is correct for displayed operand sizes (`word [ptr]` will have a
/// `MemoryAccessSize` indicating two bytes) but is _not_ sufficient to describe all accesses
/// of all instructions. the most notable exception is for operand-size-prefixed `call`, where
/// `66ff10` is the instruction `call dword [eax]`, but will push a four-byte `eip`.  tools
/// must account for these inconsistent sizes internally.
get the memory access information for this instruction, if it accesses memory.
the corresponding `MemoryAccessSize` may report that the size of accessed memory is
indeterminate; this is the case for `xsave/xrestor`-style instructions whose operation size
varies based on physical processor.
get the memory access information for this instruction if it accesses memory . the corresponding ` MemoryAccessSize ` may report that the size of accessed memory is indeterminate ; this is the case for ` xsave / xrestor ` - style instructions whose operation size varies based on physical processor .
pub fn mem_size(&self) -> Option<MemoryAccessSize> {
        if self.mem_size != 0 {
            Some(MemoryAccessSize { size: self.mem_size })
        } else {
            None
        }
    }
pub fn mem_size ( & self ) -> Option < MemoryAccessSize > { if self . mem_size != 0 { Some ( MemoryAccessSize { size : self . mem_size } ) } else { None } }
get the memory access information for this instruction, if it accesses memory.
get the memory access information for this instruction if it accesses memory .
&self
&self
note
the reported size is correct for displayed operand sizes (`word [ptr]` will have a
`MemoryAccessSize` indicating two bytes) but is _not_ sufficient to describe all accesses
of all instructions. the most notable exception is for operand-size-prefixed `call`, where
`66ff10` is the instruction `call dword [eax]`, but will push a four-byte `eip`.  tools
must account for these inconsistent sizes internally.
the reported size is correct for displayed operand sizes ( ` word [ ptr ] ` will have a ` MemoryAccessSize ` indicating two bytes ) but is _not_ sufficient to describe all accesses of all instructions . the most notable exception is for operand - size - prefixed ` call ` where ` 66ff10 ` is the instruction ` call dword [ eax ] ` but will push a four - byte ` eip ` . tools must account for these inconsistent sizes internally .