I think it does come back to Result and throw being different approaches to the same space.
Conversation
What gets my goat is that throw/try/catch could be beautiful syntactic sugar for the power of Result.
2
6
Instead, it's a bespoke, artisanal language feature that composes poorly w everything except Optional.
1
4
I disagree. Experience in Haskell shows that monadic types are awful for composing effects.
1
4
I don't understand how Optional and Result are fundamentally different here.
1
2
My point is less about The Monad and more about being able to treat maybe-errors as a value.
1
'try?' doesn't foreclose on the ability to capture a maybe-error into a value.
1
It increases the inertia of Optionalish errors rather than Eitherish errors (i.e., an afterthought).
2
I want the bad path to receive as much compositional power and valueness as the good path.
3
3
I think you have that—the thing you 'catch' is a value, not a weird reference thing like C++/Java
1
1
Replying to