3 ms·
That's not really true in practice. Often you just end up with a massive Error variant type that's used everywhere, even when the specific function you're calli
by wtetzner 3y ago
That's not really true in practice. Often you just end up with a massive Error variant type that's used everywhere, even when the specific function you're calling could only return one of them.
- WirelessGigabit 3y agoYou don't have to have Error variants if you don't care about their type. You cannot catch a StackOverflowException or an OutOfMemoryException. All you do is log it & restart the app. Once could split it into retryable errors and non-retryable ones. Like a DB disconnect, that can be retried. BUT to be fair, that's not logic that belongs in the business.