Enum Error 

#[non_exhaustive]
pub enum Error {
    BufferTooSmall {
        needed: usize,
        actual: usize,
    },
}

Errors that can occur during E2E protection or checking.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

BufferTooSmall

The output buffer is too small to hold the protected payload.

Fields

needed: usize

The number of bytes required.

actual: usize

The number of bytes available.

Trait Implementations

impl Debug for Error

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

Formats the value using the given formatter.

impl Display for Error

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

Formats the value using the given formatter.

impl Error for Error

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<Error> for Error

Bridges crate::e2e::Error onto protocol::Error so E2E failures can be reported through the same error type as the rest of the wire path.

E2E deliberately does not implement Encode/Decode (see the src/e2e module docs), so it keeps its own Error type. This impl only aligns the shape of that error with protocol::Error for callers that want a single error type to propagate; it does not change E2E’s protect/check behavior or on-wire bytes.

Mapping

e2e::Error currently has exactly one variant:

• crate::e2e::Error::BufferTooSmall { needed, actual } → maps to Error::InsufficientBuffer, not Error::Incomplete. Although Incomplete { needed, available } has the identical field shape, its semantics are decode-direction (“input ended before enough bytes could be read”). BufferTooSmall instead means an output slice was too small to hold the bytes E2E protect needed to write — the same direction as automotive_wire_codec::InsufficientBuffer (“An output slice was too small for the bytes an encode needed to write”). That is the semantically correct counterpart, so needed/actual map directly onto InsufficientBuffer’s needed/available fields.

fn from(err: Error) -> Self

Converts to this type from the input type.