error-or/error-or
Error Or
Error-or is a library that implements the result pattern to replace exception-based control flow with structured data. It provides a discriminated union implementation that encapsulates either a successful value or an error state within a single type, ensuring that operation outcomes are treated as first-class values.
The library enables functional error handling by providing a fluent interface for chaining sequential operations. This monadic pipeline composition allows developers to define dependent operations that automatically short-circuit and return an error if any individual step in the process fails.
Beyond basic result encapsulation, the project supports the management of asynchronous outcomes and provides mechanisms for validating application states. It includes utilities for transforming operation results, executing fallback logic based on success or failure, and serializing outcomes for logging or auditing purposes.
Features
- Result Patterns - Implements the result pattern to unify operation outcomes into a consistent, type-safe structure for predictable logic branching.
- Discriminated Unions - Encapsulates success and error states within a single type to enforce exhaustive handling of operation outcomes.
- Result-Based Control Flows - Replaces unpredictable exception-based control flow with explicit data structures that represent operation outcomes as first-class values.
- Result Types - Wraps operation outcomes in a structured container to replace unpredictable exception-based control flow with explicit and predictable data structures.
- Error Handling Patterns - Implements value-based error propagation to replace traditional exception-based control flow with predictable data structures.
- Monadic Computation Chaining - Enables sequential execution of dependent operations that automatically short-circuit when an error state is encountered.
- State Validation - Provides utilities to verify operation outcomes and ensure application state remains valid throughout execution.
- Exhaustive Result Handling - Forces the execution of specific functions for both success and failure variants to keep application logic organized.
- Fluent Interface Patterns - Implements a fluent API pattern that enables readable, chainable transformations of operation results.
- Fluent Interfaces - Provides a chainable method syntax that allows developers to process operation results through a readable and declarative pipeline.
- Monadic Pipelines - Supports monadic pipeline composition for sequencing dependent operations with automatic error short-circuiting.
- Exception-to-Result Adapters - Stores either a successful value or an error state within a single object to replace complex exception-based control flow.
- Result Transformations - Transforms operation results by chaining sequential operations and propagating errors through the pipeline.
- Asynchronous Result Wrappers - Integrates asynchronous tasks into result-based pipelines to maintain consistent error handling across non-blocking boundaries.
- Failure Recovery Strategies - Provides mechanisms for executing fallback logic or recovery actions when an operation encounters an error state.
- Binary Outcome State Matching - Packages successful results or error states into a single object to replace traditional exception-based control flow.
- Interdependent Operation Chaining - Executes sequences of dependent operations that automatically stop and return an error if any step fails.
- Binary Outcome Matching - Enables branching logic based on operation outcomes to ensure clean and explicit error handling throughout the codebase.
- Function Composition Operators - Enables chaining of sequential operations that automatically short-circuit when an error is encountered.
- Compile-Time Type Validation - Ensures compile-time correctness by verifying that all possible operation outcomes are explicitly handled before code execution.
