Oliver
In file 1:
defmodule Utils.Struct do
# this is for importing definitions when "use Utils.Struct" is called
defmacro __using__(_opts) do
quote do
import Utils.Struct
end
end
defmacro defstruct_module(struct_name, fields) do
quote do
defmodule unquote(struct_name) do
use Utils.Access
defstruct unquote(fields)
end
end
end
end
In file 2:
defmodule Statistical.Generator do
use Utils.Struct
@in_files [:in_cause, :out_cause, :start]
defstruct_module(State, @in_files)
Breaks:
warning: undefined module attribute @in_files, please remove access to @in_files or explicitly set it before access
<some file>: Statistical.Generator.State (module)
== Compilation error in file <some file> ==
** (ArgumentError) struct fields definition must be list, got: nil
(elixir 1.14.4) lib/kernel/utils.ex:117: Kernel.Utils.defstruct/3
But this works - again file 2:
defmodule Statistical.Generator do
use Utils.Struct
@in_files [:in_cause, :out_cause, :start]
in_files = @in_files
defstruct_module(State, in_files)
By the way, if I use the variable approach instead of the module attribute, than the def blocks of the module in file 2 complain… can’t win? ![]()
Is this because the it inserts the module attribute verbatim as abstract syntax tree? Is there a construct/pattern to handle this case - like would a bind_quote help?
Thank you!
Trending in Questions
I’m aware of 2 such projects, are there others?
git: GitHub - team-alembic/realworld: A fullstack Phoenix LiveView application with back...
New
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
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
Hi,
we run different LLM models across a cluster, with each node loading a configurable subset. Model-specific queues let nodes consume ...
New
Other Trending Topics
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
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
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
- #performance










Showing Posts 1 to 6- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
DaAnalyst
To use the module attributes in your macro, you’ll need to do it in
__before_compile__/1.Take a look at this upgrade of my library which was done precisely for the same reason
(see the difference between v0.2.0 and v0.1.0) - kudos and thanks to @kip
https://github.com/DaTrader/assigns
Oliver
If I understand your code correctly it tries to find an attribute in the calling module and use it in the macro.
I think my scenario is a bit different - I’m trying to pass a value to the macro, and it’s not always a module attribute either. I typically call it like this:
If I understand what you’re doing, it might be possible to match for “module attribute” in a separate head for the same macro and then use
Module.get_attribute/3and call the other Macro head with it?We tried
Macro.expand(param, __CALLER__)and it remained nil.If you meant something else, please let me know.
DaAnalyst
No, it’s the same case. My lib is also mostly taking lists of atom keys as such, but I needed it to support taking a module attribute as well, hence the change.
josevalim
Correct. You could instead first unquote it in its actual scope:
Oliver
Thank you both!
Let me preface this with the fact that I can live with adding an extra variable on top-level by hand if that’s easiest.
But I still want to follow up with you.
@josevalim - I tried your solution, and it works for the module atttribute case.
Another use case then has a different problem:
Will result in:
I assume this is due to the fields list being expanded now outside the
defmoduleand compiled before that “inner module” was compiled yet?The original version worked with that scenario where the list was given directly.
I tried bind_quoted but then I also need to use it on
struct_namefield and then aliases are expanded differently (and no longer include the name of any module defined one level higher).It’s a tricky one… There’s always a scope where it doesn’t come together.
@DaAnalyst -
I know it’s on me / is my fault, but I’m looking at the diff of your project and I just can’t see how that pertains to my problem. My mind doesn’t make the connection.
DaAnalyst
If you look at my lib code, you’ll see that in its first version (0.1.0) it simply relied on the vanilla macros to expand the
def assign_*and friends. The problem with that approach was that it could only take a list of atoms and not a module attribute (to which a list of atoms is assigned) because the module attribute was not resolvable at the time of the macro expansion. The__before_compile__/1approach that was suggested by @kip solved this (as shown in the version 0.2.0) because at the time it expands it can resolve the module attributes, hence the necessary refactoring.