riccardomanfrin
I’m trying to understand how macros and module definitions interact with each others and I’m having few cases which I don’t understand. The below example has some pseudo doctest to show my doubts.
What I need is to support case 5. Thanks for the support in advance
defmodule Foo do
@doctest """
Case 1 OK: Trivial (and useless) case.. (Foo.Case1)
iex> Foo.Case1.foo
"local stuff"
Case 2 OK: Injects the Case2 in WrapMod and uses its args
WARNING: comment Case4 for this to work (head scratching)
iex> WrapMod.Case2.foo
[foo: "bar"]
Case 3 FAILED!!!! Injects used args into the Foo.Case3.foo function
Error:
example.ex:24: undefined function args/0 (expected Foo.Case3 to define
such a function or for it to be imported, but none are available)
Desiderata:
iex> Foo.Case3.foo
[foo: "bar"]
Case 4 KINDA NOT OK: Super clunky combo of case 2 and 1
It works, but it HIDES!!!!! Case 2: Call to `WrapMod.Case2.foo` is not available
anymore
iex> WrapMod.Case4.foo
"local stuff"
iex> WrapMod.Case2.foo
UndefinedFunctionError
Case 5 FAILED: Hyper clunky combo of case 2 with case 3 <- which is not working :(
This is where I'd want to get to: I would like to be able to invoke
and use the evaluated Foo.Case3.foo from within the quoted Case5 quoted module code
"""
defmacro __using__(args) do
#Case 1
defmodule Case1 do
def foo() do
"local stuff"
end
end
#Case 2
quote do
defmodule Case2 do
def foo() do
unquote(args)
end
end
end
#Case 3
#defmodule Case3 do
# def foo() do
# quote do
# unquote(args)
# end
# end
#end
# Case 4: comment me to get back WrapMod.Case2.foo which is otherwise no more available!!!
quote do
defmodule Case4 do
def foo() do
Case1.foo()
end
end
end
#quote do
# defmodule Case5 do
# def foo() do
# Case3.foo()
# end
# end
#end
end
end
defmodule WrapMod do
use Foo, foo: "bar"
end
For the records, case 3 works if I change it like this:
#Case 3
defmodule Case3 do
def foo() do
quote do
var!(args)
end
end
end
but this is giving me
iex(1)> Foo.Case3.foo
{:var!, [context: Foo.Case3, import: Kernel], [{:args, [], Foo.Case3}]}
which is clearly not what I want
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Hello all. I have a question as to best practices for code organization when implementing a liveview with a lot of responsibilities.
Sup...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #elixirconf-us
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
riccardomanfrin
I figured how to sort out the reason why Case4 obliterates Case2. Injection through
quoteexpands the AST returned by the__using__macro. In order to expand both cases, they need to stay together a the end of the__using__macro and wrapped into a list:fuelen
As in regular functions, macro returns the last expression.
It is not necessary to wrap two quote expressions into a list. You can simply wrap both module definitions into 1 quote block: