any_of 1.3.3

A general optional sum of product type which can be Neither, Left, Right or Both.
Documentation
# AnyOf : a versatile type for Rust

[![Rust](https://github.com/Trehinos/any_of/actions/workflows/rust.yml/badge.svg?branch=ci)](https://github.com/Trehinos/any_of/actions/workflows/rust.yml)

This project implements a flexible [Algebraic Data Type](https://en.wikipedia.org/wiki/Algebraic_data_type) : `AnyOf`.

`AnyOf` is an optional **sum of product of two types**,  
which enables clear and safe data representations in functional and type-driven programming.

## Overview

At the core of the project is the `AnyOf` enum, a general-purpose algebraic type,
alongside additional types as `Either` and `Both`.

These abstractions allow to express dynamic states, optional values, and branching logic in a natural and explicit
manner.

### Key Types

1. **`AnyOf<L, R>`**
    - A flexible type that represents four possible states:
        - `Neither`: No value is present.
        - `Either::Left`: Only the left value is present.
        - `Either::Right`: Only the right value is present.
        - `Both`: Both values are present.
    - Conceptually, it combines variants in the following way:
      ```
      AnyOf<L, R> = Neither | Either<L, R> | Both<L, R>
      ```
    - Its cases are:
      ```
      AnyOf(L, R) = Neither | Either::Left(L) | Either::Right(R) | Both(L, R)
      ```
    - It can also be viewed as a product of two optional types:
      ```
      AnyOf<L, R>::any = (Option<L>, Option<R>)
      ```
      Cases :
        - `Neither::any` = `(None, None)`
        - `Either::Left(L)::any` = `(Some(L), None)`
        - `Either::Right(R)::any` = `(None, Some(R))`
        - `Both::any` = `(Some(L), Some(R))`

2. **`Either<L, R>`**
    - A simple sum type representing one of two values.
    - Variants:
        - `Left(L)`
        - `Right(R)`
    - Ideal for binary decision-making.
    - Conceptually, it is the type :
      ```
      Either<L, R> = Left(L) | Right(R)
      ```

3. **`Both<L, R>`**
    - A product type that pairs two values, `left` and `right`, of potentially different types.
    - Conceptually, it is the type:
      ```
      Both<L, R> = (L, R)
      ```

4. **Enhanced Type Composition**
    - Complex types like `AnyOf4`, `AnyOf8`, and `AnyOf16` are implemented for handling larger,
      structured combinations via nested `AnyOf` structures.
    - The `LeftOrRight` trait :
        - Provides the methods `is_right()`, `is_left()`, `any()`, `left()` and `right()`.
        - Implemented by `AnyOf`, `Either` and `Both`,
        - Can be implemented by a custom type.
    - Other useful traits : `Unwrap<L, R>`, `Swap<L, R>` and `Map<L, R>`.

### Features and Utilities

- Methods inspired by Rust's `Option` and `Result` types:
    - Creation utilities: `new`, `new_left`, `new_both`, etc.
    - State checks: `is_neither`, `is_left`, `is_both`, etc.
    - Transformations: `map_left`, `map_right`, `swap`, etc.
    - Unwrapping: `unwrap_left`, `unwrap_right`, `unwrap_both`.

- Flexible combinations:
    - Operators :
        - `&` to combine `AnyOf` values, or,
        - `|` to filter `AnyOf` values, or,
        - `!` to swap  `AnyOf`, `Either` and `Both` values.
    - Default value handling and state manipulation methods.

![Type diagram PNG](doc/any_of-type-diagram.png)

[Download the type diagram](doc/types.plantuml).

### Use Cases

`AnyOf` and its related types simplify dynamic state management and are well-suited for:

- Branching logic in functional programming.
- Handling optional or partial data.
- Implementing explicit and exhaustive handling of all potential states.
- Minimizing boilerplate for complex decision-making.

## Motivation

The project aims to enrich Rust's type system with expressive and flexible types
for representing data combinations and states.

* Unlike the Rust's `Result` type, `AnyOf`, `Either` or `LeftOrRight` have not an "error" semantic, it is general purpose,
* All `LeftOrRight<L, R>::any` can be represented by a `(Option<L>, Option<R>)`  which is a product of two optional types,

## Status

The library may evolve following **semantic versioning**,
so the API will be stable in a given major version.

[Feedback is welcome](mailto:dev-any-of@trehinos.eu)!

## License

&copy; 2025 Sébastien Geldreich  
Distributed under the MIT License.