zerovec::ule

Trait VarULE

Source
pub unsafe trait VarULE: 'static {
    // Required methods
    fn validate_bytes(_bytes: &[u8]) -> Result<(), UleError>;
    unsafe fn from_bytes_unchecked(bytes: &[u8]) -> &Self;

    // Provided methods
    fn parse_bytes(bytes: &[u8]) -> Result<&Self, UleError> { ... }
    fn as_bytes(&self) -> &[u8]  { ... }
    fn to_boxed(&self) -> Box<Self> { ... }
}
Expand description

Variable-width, byte-aligned data that can be cast to and from a little-endian byte slice.

If you need to implement this trait, consider using #[make_varule] or #[derive(VarULE)] instead.

This trait is mostly for unsized types like str and [T]. It can be implemented on sized types; however, it is much more preferable to use ULE for that purpose. The custom module contains additional documentation on how this type can be implemented on custom types.

If deserialization with VarZeroVec is desired is recommended to implement Deserialize for Box<T> (serde does not do this automatically for unsized T).

For convenience it is typically desired to implement EncodeAsVarULE and ZeroFrom on some stack type to convert to and from the ULE type efficiently when necessary.

§Safety

Safety checklist for VarULE:

  1. The type must not include any uninitialized or padding bytes.
  2. The type must have an alignment of 1 byte.
  3. The impl of VarULE::validate_bytes() must return an error if the given byte slice would not represent a valid slice of this type.
  4. The impl of VarULE::validate_bytes() must return an error if the given byte slice cannot be used in its entirety.
  5. The impl of VarULE::from_bytes_unchecked() must produce a reference to the same underlying data assuming that the given bytes previously passed validation.
  6. All other methods must be left with their default impl, or else implemented according to their respective safety guidelines.
  7. Acknowledge the following note about the equality invariant.

If the ULE type is a struct only containing other ULE/VarULE types (or other types which satisfy invariants 1 and 2, like [u8; N]), invariants 1 and 2 can be achieved via #[repr(C, packed)] or #[repr(transparent)].

§Equality invariant

A non-safety invariant is that if Self implements PartialEq, the it must be logically equivalent to byte equality on Self::as_bytes().

It may be necessary to introduce a “canonical form” of the ULE if logical equality does not equal byte equality. In such a case, Self::validate_bytes() should return an error for any values that are not in canonical form. For example, the decimal strings “1.23e4” and “12.3e3” are logically equal, but not byte-for-byte equal, so we could define a canonical form where only a single digit is allowed before ..

There may also be cases where a VarULE has muiltiple canonical forms, such as a faster version and a smaller version. The cleanest way to handle this case would be separate types. However, if this is not feasible, then the application should ensure that the data it is deserializing is in the expected form. For example, if the data is being loaded from an external source, then requests could carry information about the expected form of the data.

Failure to follow this invariant will cause surprising behavior in PartialEq, which may result in unpredictable operations on ZeroVec, VarZeroVec, and ZeroMap.

Required Methods§

Source

fn validate_bytes(_bytes: &[u8]) -> Result<(), UleError>

Validates a byte slice, &[u8].

If Self is not well-defined for all possible bit values, the bytes should be validated. If the bytes can be transmuted, in their entirety, to a valid &Self, then Ok should be returned; otherwise, Self::Error should be returned.

Source

unsafe fn from_bytes_unchecked(bytes: &[u8]) -> &Self

Takes a byte slice, &[u8], and return it as &Self with the same lifetime, assuming that this byte slice has previously been run through Self::parse_bytes() with success.

§Safety
§Callers

Callers of this method must take care to ensure that bytes was previously passed through Self::validate_bytes() with success (and was not changed since then).

§Implementors

Implementations of this method may call unsafe functions to cast the pointer to the correct type, assuming the “Callers” invariant above.

Safety checklist:

  1. This method must return the same result as Self::parse_bytes().
  2. This method must return a slice to the same region of memory as the argument.

Provided Methods§

Source

fn parse_bytes(bytes: &[u8]) -> Result<&Self, UleError>

Parses a byte slice, &[u8], and return it as &Self with the same lifetime.

If Self is not well-defined for all possible bit values, the bytes should be validated, and an error should be returned in the same cases as Self::validate_bytes().

The default implementation executes Self::validate_bytes() followed by Self::from_bytes_unchecked.

Note: The following equality should hold: size_of_val(result) == size_of_val(bytes), where result is the successful return value of the method. This means that the return value spans the entire byte slice.

Source

fn as_bytes(&self) -> &[u8]

Given &Self, returns a &[u8] with the same lifetime.

The default implementation performs a pointer cast to the same region of memory.

§Safety

Implementations of this method should call potentially unsafe functions to cast the pointer to the correct type.

Source

fn to_boxed(&self) -> Box<Self>

Allocate on the heap as a Box<T>

Dyn Compatibility§

This trait is not dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety", so this trait is not object safe.

Implementations on Foreign Types§

Source§

impl VarULE for str

Source§

unsafe fn from_bytes_unchecked(bytes: &[u8]) -> &Self

Invariant: must be safe to call when called on a slice that previously succeeded with parse_bytes

Source§

fn validate_bytes(bytes: &[u8]) -> Result<(), UleError>

Source§

fn parse_bytes(bytes: &[u8]) -> Result<&Self, UleError>

Source§

impl<T> VarULE for [T]
where T: ULE,

Note: VarULE is well-defined for all [T] where T: ULE, but ZeroSlice is more ergonomic when T is a low-level ULE type. For example:

// OK: [u8] is a useful type
let _: VarZeroVec<[u8]> = unimplemented!();

// Technically works, but [u32::ULE] is not very useful
let _: VarZeroVec<[<u32 as AsULE>::ULE]> = unimplemented!();

// Better: ZeroSlice<u32>
let _: VarZeroVec<ZeroSlice<u32>> = unimplemented!();
Source§

fn validate_bytes(slice: &[u8]) -> Result<(), UleError>

Source§

unsafe fn from_bytes_unchecked(bytes: &[u8]) -> &Self

Implementors§

Source§

impl<A, V> VarULE for VarTupleULE<A, V>
where A: AsULE + 'static, V: VarULE + ?Sized,

Source§

impl<A: VarULE + ?Sized, B: VarULE + ?Sized, C: VarULE + ?Sized, D: VarULE + ?Sized, E: VarULE + ?Sized, F: VarULE + ?Sized, Format: VarZeroVecFormat> VarULE for Tuple6VarULE<A, B, C, D, E, F, Format>

Source§

impl<A: VarULE + ?Sized, B: VarULE + ?Sized, C: VarULE + ?Sized, D: VarULE + ?Sized, E: VarULE + ?Sized, Format: VarZeroVecFormat> VarULE for Tuple5VarULE<A, B, C, D, E, Format>

Source§

impl<A: VarULE + ?Sized, B: VarULE + ?Sized, C: VarULE + ?Sized, D: VarULE + ?Sized, Format: VarZeroVecFormat> VarULE for Tuple4VarULE<A, B, C, D, Format>

Source§

impl<A: VarULE + ?Sized, B: VarULE + ?Sized, C: VarULE + ?Sized, Format: VarZeroVecFormat> VarULE for Tuple3VarULE<A, B, C, Format>

Source§

impl<A: VarULE + ?Sized, B: VarULE + ?Sized, Format: VarZeroVecFormat> VarULE for Tuple2VarULE<A, B, Format>

Source§

impl<T: AsULE + 'static> VarULE for ZeroSlice<T>

Source§

impl<T: VarULE + ?Sized + 'static, F: VarZeroVecFormat> VarULE for VarZeroSlice<T, F>

Source§

impl<U: VarULE + ?Sized> VarULE for OptionVarULE<U>

Source§

impl<const LEN: usize, Format: VarZeroVecFormat> VarULE for MultiFieldsULE<LEN, Format>