Skip to main content

Functional - UnambitiousFx

Result, Maybe, and railway-oriented error handling for .NET — zero-allocation and Native-AOT ready.

Get Started →View on GitHub
dotnet add package UnambitiousFx.Functional
Quick start
// Compose with railway-oriented programming
public Result<Order> PlaceOrder(OrderRequest request) =>
    Validate(request)               // Result<OrderRequest>
        .Bind(LoadCustomer)         // Result<Customer>
        .Ensure(c => c.IsActive,
            new ValidationFailure("Customer is inactive"))
        .Map(CreateOrder)           // Result<Order>
        .Tap(order => _log.Created(order.Id));

// Pattern match — errors are values, not exceptions
var response = PlaceOrder(request).Match(
    success: order => Results.Ok(order),
    failure: error => Results.BadRequest(error.Message));

// Optionals without null
Maybe<User> user = _users.TryFind(id);
string name = user
    .Map(u => u.Name)
    .ValueOr("anonymous");

Why Functional?

🚂

Result & Railway

Model success and failure as one type. Chain Bind, Map, and Ensure — the first failure short-circuits the rest. Errors are values, not exceptions.

🎁

Maybe / Optionals

Represent "a value or nothing" without null. Compose with Map, Filter, and OrElse, then bridge to Result when you need a reason.

🏷️

Rich Failures

Typed failures — validation, not-found, conflict, unauthorized — each with a machine-readable code and attachable Metadata. Aggregate many into one.

⚡

Zero-Allocation & AOT

Core types are readonly structs with ValueTask-based async. Minimal heap traffic in hot paths and fully Native-AOT compatible.

Explore the docs

🚀

Getting Started

Install the package and write your first Result.

🚂

Result

Railway-oriented composition: Bind, Map, Ensure, Recover.

🎁

Maybe

Optional values without null — Some, None, and friends.

🧪

Testing

Fluent assertions for Result and Maybe with Functional.xunit.