Expand description
§rancor
rancor provides scalable and efficient error handling without using type composition. This makes it best-suited for situations where:
- Programmatic error introspection is not useful
- Functions may error, but succeed most of the time
- Errors should provide as much useful detail as possible when emitted
- Use cases include both
no_stdand targets with support forstd
§Features
alloc: Provides theBoxedErrortype. Enabled by default.
Macros§
- fail
- Returns the given error from this function.
Structs§
- Boxed
Error alloc - An error type that preserves all detailed error messages. It is optimized to fit in a single pointer.
- Error
- A good general-purpose error type.
- Failure
- An error type that only preserves success or failure, throwing away any more detailed error messages.
- Strategy
- Equips a type with a
Fallibleimplementation that choosesEas its error type.
Enums§
- Infallible
- A re-export of
core::convert::Infallible. The error type for errors that can never happen. - Panic
- An error type that does not occupy any space, panicking on creation instead.
Traits§
- Fallible
- A type with fallible operations that return its associated error type.
- Never
- A type that can never be produced.
- Option
Ext - Helper methods for
Options. - Result
Ext - Helper methods for
Results. - Source
- An error type which can be uniformly constructed from an
Errorand additional trace information. - Trace
- An error type which can add additional “trace” information to itself.
Functions§
- unreachable_
checked - Consumes a
Nevertype, returning a primitive!.