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
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
New
Other Trending Topics
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
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 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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming










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: