stephanos
Hi!
I’ve been tinkering with bringing Clojure.spec to Elixir (I’m aware of prior art here, but want to experiment with a different syntax).
Having never dabbled in meta programming before, I’m curious to learn if I hit a wall or if I’m missing something.
Here is some simple pseudo-code
@arg a: is_integer(), is_integer()
@arg b: is_integer()
@ret is_integer()
def add(a, b) do
a + b
end
I discovered that @ is a macro in the Kernel module and appears to be evaluated before I get a chance to do anything (via before_compile, on_definition or my macro). Right now it fails because is_integer() isn’t valid.
Is there any way to transform the AST to replace the module attribute with my own code?
I’ve learned about the possibility of a custom defmodule implementation but that seems excessive to me. I considered using function references, like &is_integer/1 but it seems a bit ugly to me (very subjective ;). It also appears that I can’t override the @ macro easily since I’m getting “call is ambiguous” when I define my own. Are these all available options?
Thank you!
Stephan
Where Next?
Trending in Discussions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
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
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
christhekeele
Hey, welcome to the ElixirForum, and Elixir meta-programming!
I think the conceptual nudge that will help you the most here is a little clarification in the role of various concepts during the compilation process:
Moduleis a unit of compilation + a namespacemodule attributeis a constant language-level value determined at compile timeMacrois a special function executed at compile time that receives AST as input and places its return value into the AST where invokedEmphasis on value. What you place in a module attribute should be a language-level primitive value, that may be operated on later by compile-time hooks. You’ll notice the input to all documented module attributes, with the exception of type-related stuff, are just tuples, lists, strings, atoms, etc.
Typespec-related attributes get special builtin compiler-powered semantics and expressivity, that I do not think you can tap into in user-land code.
You cannot place arbitrary typespec syntax into an arbitrary module attribute today.
The easiest way to get this is to use macros, which specialize in AST transformation. You should try offering, for instance,
defarganddefretmacros. They could emit type-spec related module attributes AST compatible with the type system. Macros are more than capable of consuming the typespec syntax and operating on it, doing library magic with it, and re-emitting the syntax into typespec module attributes.As an alternative, you could invent a language-level data primitive syntax that expresses what you want, like
@arg a: [:is_integer, :is_integer], and compile it into a typespec via a compilation hook (and perform your library’s magic in the same pass).The takeaway here, though, is that you’ll need to leverage macros get what you want, with module attributes as possible input to them and output from them.
One note:
You definitely don’t want to do this–even if it is possible (which would surprise me) overriding module attribute definition would have a high chance of breaking tons of stuff in caller code.
@is a macro in theKernelmodule for documentation and compiler bootstrapping purposes only.Qqwy
Overriding the
@-macro is possible, and is in fact whatNormdoes to allow custom macro-expansion in the ‘@contract …’ notation. (c.f. norm/lib/norm/contract.ex at master · elixir-toniq/norm · GitHub)I do think that this solution is a bit of a hack. For instance, it would not be possible to use multiple libraries that each try to override
@unless they pay special attention to how they do the fall-back.stephanos
@christhekeele Thank you, I really appreciate that insight - and the warm welcome!
@Qqwy ha, I guess I wasn’t aware of this Clojure.spec-like implementation - that’s pretty close to what I was imagining. The generator-side of this is what I find the most intriguing.
christhekeele
That’s pretty cool. Still dark magicks, but now I wanna play with it!