Enum ErrorStrategy 

pub enum ErrorStrategy {
    Throws,
    Trap,
}

How a callable’s out_err slot is interpreted by idiomatic wrappers.

Every synchronous C ABI entry point carries a trailing out_err, and every async completion callback carries an err slot, regardless of throws. What differs is the meaning of a non-zero code, and every backend must agree on it.

Variants

Throws

The function declares throws: true: a non-zero code is a typed domain error. The wrapper maps the code onto the module’s error domain (an exception subclass, a Swift Error enum case, a Go error value, …) and surfaces it through the target’s normal error channel so callers can catch and match on it.

Trap

The function does not throw: the only way out_err reports failure is a producer bug (most commonly a caught panic, code -2). The wrapper surfaces it through the target’s programming-error idiom (a Python WeaveFFIError, a Go panic, a Swift fatalError, a C# exception). It must never be silently ignored, and it must never be dressed up as a typed domain error.

Trait Implementations

impl Clone for ErrorStrategy

fn clone(&self) -> ErrorStrategy

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Copy for ErrorStrategy

impl Debug for ErrorStrategy

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

Formats the value using the given formatter.

impl Eq for ErrorStrategy

impl PartialEq for ErrorStrategy

fn eq(&self, other: &ErrorStrategy) -> bool

Equality operator ==.

fn ne(&self, other: &Rhs) -> bool

Inequality operator !=.

impl StructuralPartialEq for ErrorStrategy