miguelszerman
What is considered 'bad' in a guard clause?
Inside the Elixir official documentation, the guards sections states:
Not all expressions are allowed in guard clauses, but only a handful of them. This is a deliberate choice. This way, Elixir (and Erlang) can make sure that nothing bad happens while executing guards and no mutations happen anywhere. It also allows the compiler to optimize the code related to guards efficiently.
What does ‘bad’ mean here? Is it only referring to mutations and non-optimizable code?
Most Liked
hst337
Patterns and Guards are a small separate language inside Elixir (and Erlang). Compiler takes a look at the guards and patterns and generates very efficient BEAM assembly. Therefore, guards are limited only to a set of declarative functions which you can find here (for erlang) and here (for elixir)
For example,
case something do
1 -> ...
2 -> ...
3 -> ...
a when is_atom(a) -> ...
b when is_binary(b) -> ...
end
Will generate a jump table, and switching in this kind of case will always be O(1)
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Courses that'll move you from confusion to "Aha, now I get it!"
Categories:
Sub Categories:
Forums
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"