On 19/12/2025 01:24, Eric Kolotyluk wrote:
:
So while Joiners make join() result-producing and more configurable,
the failure channel is still exception-based. From that perspective, I
can still see value in a functional, value-oriented result type—where
success and failure are both represented explicitly as
values—coexisting alongside exceptions, rather than routing expected
failure exclusively through throws.
With records, sealed classes, pattern matching, ... then you should have
enough to have the outcome from your own Joiner use ADTs to abstract
over the success and failures cases. Maybe try that and write up your
experiences?
-Alan
