The Result pattern: errors without exceptions in C#

Exceptions for business flow hide error paths and make tests verbose. The Result pattern makes failures explicit in the return type.

Minimal shape

public readonly record struct Result<T>
{
    public T? Value { get; }
    public Error? Error { get; }
    public bool IsSuccess => Error is null;
}

Where to use it

Input validation, domain rules, external calls with expected failure — all fit Result. Save exceptions for bugs and truly exceptional failures (OOM, unexpected network down).

Turning try/catch into if (result.IsFailure) looks like more code, but the compiler starts reminding you to handle the error. In APIs, map Error to HTTP status centrally.