voger
Can someone please explain this 'my_if' code in the Metaprogramming Elixir book?
I just finished “Programming Elixir” and now I am reading “Metaprogramming Elixir”. I can’t say I comprehend everything. I try to understand but I mostly pretend I understand and keep reading. While the previous examples were somehow manageable to follow I am stuck in recreating the if macro. Here is the code.
defmodule ControlFlow do
defmacro my_if(expr, do: if_block) do
if(expr, do: if_block, else: nil)
end
defmacro my_if(expr, do: if_block, else: else_block) do
quote do
case unquote(expr) do
result when result in [false, nil] -> unquote(else_block)
_ -> unquote(if_block)
end
end
end
end
Can someone please be patient and explain with simple words what is happening in this code?
I understand what quote and unquote do. I don’t understand why the two defmacro definitions.
Now that I write the question I realize the first defmacro is just for the case we have a simple if without else. The second defmacro handles the if/else case. But still I can’t understand how they work.
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated!
To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead.
Sta...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #performance










First 10 of 11 Posts
brainbag
If you understand that code like this:
is simply syntactic sugar for this:
and that is simply syntactic sugar for this:
and THAT is simply syntactic sugar for this:
then it might be a bit clearer. Remember that Elixir allows you to drop the List
[]if you’re passing in a keyword list.Some more detail: your first
my_iffunction takes two arguments, one of which is an explicit keyword list ofdo:. Sinceelseisn’t specified, it just passesnilin for theelse. That will run when you call code like this:Your second
my_iffunction does a case statement on the expression (somethingin my example). Inside of the case statement, it checks to see if the result evaluation is one offalseornil, and then returns theelse_block. Otherwise, it returns theif_block.You might check the “Keywords and maps” section of the documentation for further reference: http://elixir-lang.org/getting-started/keywords-and-maps.html
Hope that helps!
voger
Thanks. It did help a lot. Also I had to research more how “case” works in Elixir.
But I still have another problem with this code. I even copy pasted the from the book to my editor but still get the same result.
Here is the original code for the first my_if macro from the book
here is the result I get in iex
In lines 27 and 28 shouldn’t the if statement return nil?
brainbag
No, because you forgot something very important in your first definition.
If you do an
IO.inspectin that firstmy_if, what is the value ofexpr? It’s not what you think!When you figure that out, think about how you “transform” values so they’re usable by macros, and then look at your first
my_ifagain and see what you’re missing.voger
Wow thanks. I already tried to use unquote but I got errors because I didn’t wrap it first in “quote do”. The correct code is this
Thank you very much for your help.
kodepett
I faced the same issue will working through Metaprogramming Elixir. my_if returns true irrespective of the condition when invoked without the else block. I think it’s an errata, I supposed the line should be:
Below is the full snippet from the book on page 22, maybe @chrismccord can clarify, I could be wrong with my assumption.
chrismccord
Using the provided snippet from the book:
Are you sure your code is correct wherever you are running it?
kodepett
Hi, kindly find below - elixir v1.13.3
LostKobrakai
Shouldn’t the first macro body delegate to
my_if, notif?kodepett
I tried that and had an error
cannot invoke macro my_if/2 before its definitionchrismccord
Bah, yes it is indeed erratta. You’re the first to catch this in like 8 years!
If you give in a non AST literal, it’s always true because we are passing the ast to
ifin the first clause, not the expanded expression. So for example,1 > 2will be the ast tuple, instead of the boolean, which is always truthy. The code should have quoted the first clause. As @LostKobrakai said tho, a better example wouldn’t proxy to Elixir’s if in the first place: