Streamlining Unwieldy Type Signatures in Option-Based Code
the type signatures for Option based code seem unwieldy because the type parameter is on the functions, there's no
I know why (convention/treeshaking etc) - just wondering if anyone has an approach that reads nicer than
Option<T> I know why (convention/treeshaking etc) - just wondering if anyone has an approach that reads nicer than
Effect.Effect<Option.None<T> | Option.Some<T>, E> ?
