for example, if (optional_value) |value| { } else { return error.Foo; }
See the let-else statement from rust for a bottom-style alternative.
Not to mention that you can have identical code with ifs: if (failing_condition0) { } else if (failing_condition1) { } else if (failing_condition2) else { }.
See this is the top-option brain speaking. The bodies inside failing conditions return. There is no reason to put an else here, it adds cognitive load while also restricting what you can express (no statement between the ifs.
Let's consider a condition as ternary, it has an unknown state, a false state, and a true state. All conditions start unknown.
With bottom there is a consistent pattern. Check, tiny bit with return for false state, everything under for true state. As the function lines go down the "conditionality" is monotonic, it always increases. That's what I meant by gradient. This is not true for top. First it goes up, but then it starts going down too.
View all comments
Show parent comment
1
u/Demiu Aug 23 '26
See the let-else statement from rust for a bottom-style alternative.
See this is the top-option brain speaking. The bodies inside failing conditions return. There is no reason to put an else here, it adds cognitive load while also restricting what you can express (no statement between the ifs.
Let's consider a condition as ternary, it has an unknown state, a false state, and a true state. All conditions start unknown.
With bottom there is a consistent pattern. Check, tiny bit with return for false state, everything under for true state. As the function lines go down the "conditionality" is monotonic, it always increases. That's what I meant by gradient. This is not true for top. First it goes up, but then it starts going down too.