effect-pattern-matching

Use Data.TaggedEnum with the $match utility to get exhaustive, type-safe pattern matching for tagged variants in Effect v4. This replaces manual tag checks, ensuring all variants are handled correctly as your discriminated unions evolve.

Prefer Effect.match over combining Effect.result with manual conditional checks. Effect.match declaratively forces you to handle both success and failure paths exhaustively, preventing silent failures and improving pipeline maintainability.

Use Match.typeTags to perform exhaustive pattern matching on Schema-based unions. This ensures your workflow and state logic remain correct and type-safe as new variants are added to your schema definitions.

Replace manual _tag conditional branching when implementing state machines, domain events, or error-handling pipelines that must remain exhaustive. Using $match and $is guards ensures your code stays correct as variants change over time.

Yes, use Option.match to handle Option types exhaustively. It provides a declarative way to manage both Some and None cases, replacing partial unwrapping and ensuring your functional control flow is completely type-safe.