hpjm
Hi everyone! I’m trying to understand this piece of Mox source code.
I get the part of adding the behaviour attribute to the generated module, but why is the reference to the behaviour module included by itself 
? Not seen this pattern before. I guess the clue is in the function name, but I wanted to be sure.
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Practical resources that improve the lives of professional developers.
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
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
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)
ityonemo
Yep, super strange that it isn’t just
unquote(behaviour)If I had to guess it might be an aliasing thing, but that still doesn’t make sense to me.
LostKobrakai
module_infomight trigger some cache busting or otherwise refreshing of all implementations of the behaviour.al2o3cr
Digging through the source history, that generated call to
module_infopredates the use of@behaviourand was originally introduced to ensure that the generated module recompiled at the correct times:https://github.com/dashbitco/mox/issues/23
A generated
@behaviourline was added later, and without disturbing the existing line:https://github.com/dashbitco/mox/pull/90
ityonemo
Lol that’s my pr!