Re:Core Erlang by Example
by patrec on Monday May 07, 2018 @04:58PM
(#17016439)
The flipside is that in Erlang often need repetitive code like so:
whereas in ocaml (and F#, modulo details) you could just do something like:
The examples are unidiomatic and artificial and you can sometimes ameliorate it with guards, but it's a frequent (minor) annoyance.
[ Parent
| on HN ]
Close enough?
case X of
{Cat, N} when Cat == expense; Cat == invoice; Cat == loss -> Total - N;
{credit, N} -> Total + N
endpatrec said that
> you can sometimes ameliorate it with guards
which is exactly what you did, so I don't think you're disagreeing here :)
That's a neat pattern in F#, I like it!
In Erlang's case (pun intended!) I'd probably go for a function though:
total({expense, N}, Total) -> Total - N;
total({invoice, N}, Total) -> Total - N;
total({loss, N}, Total) -> Total - N;
total({credit, N}, Total) -> Total + N.That still repeats the `Total - N` 3 times, though. As patrec said, it's possible to work around this with guards in this specific case, but in general this kind of duplication is indeed common in Erlang code. You can avoid it many cases by correctly factoring the code, but it's not always possible and then it's a bit irritating. Not too much, though. It's basically the difference between fall-through and non-fall-through `switch` statement: OCaml/F# allow fall-through (as an option, not by default, thankfully), Erlang/Elixir/LFE don't.