Why do some people shun `if`?
Mon Aug 16 09:01:33 CEST 2021
My reason for avoiding "if" in Erlang is that it doesn't do what I expect,
so I am likely to get it wrong. From using many many other programming
languages, I expect 'if <expression>', but in Erlang it's 'if <guard>'. To
add to the confusion, instead of separating guards and expressions
even more clearly, Erlang has blurred them further. So sometimes
making that mistake will have no consequences, and other times it will
make me sorry. It's one of those things like writing
<constant> == <variable>
<variable> == <constant>
in C, to avoid the error of writing = instead of ==.
On Sun, 15 Aug 2021 at 09:45, Michael P. <empro2@REDACTED> wrote:
> I once stumbled over someone's Erlang style guide,
> they wanted no `if`.
> It was not very well explained why,
> and there was no obvious e-mail address,
> or I wanted to first do
> some thorough thinking about it.
> Now I have no more than this:
> Is if not merely "syntactic sugar" for
> a fun/0 with guarded clauses?
> Now_this_is = (fun If() when Guard_seq_1 -> Expr_seq_1
> %% On and on and on
> ; If() when Guard_seq_N -> Expr_seq_N
> % or:
> Worst = case true
> of true when Guard_seq_1 -> Expr_seq_1
> ; true when Guard_seq_2 -> Expr_seq_2
> What could be perceived as wrong with `if`?
> But who will test the tests?
More information about the erlang-questions