[erlang-questions] Why does Core Erlang have a catch-all clause for everything?
Fri Jan 19 11:48:20 CET 2018
It is undefined behaviour from Core Erlang's POV to have a value that doesn't match against any case arm. There are other similar UB cases, such as a Core Erlang clause guard not evaluating to a boolean.
See the spec for more details.
> Le 19 janv. 2018 à 11:45, Loïc Hoguin <essen@REDACTED> a écrit :
> A short discussion about exceptions left us wondering why generated Core Erlang code always has a catch-all clause for things that don't match? Is it so it can throw a specific exception? And what would happen if the catch-all was missing and the input failed to match?
> Loïc Hoguin
> erlang-questions mailing list
More information about the erlang-questions