hst337
Inter-module dependency tracing bug
Consider this module
defmodule XXX do
module = String.to_atom("Elixir." <> "YYY")
@x apply(Enum.at([module, ZZZ], 0), :func_y, [0])
def x do
@x
end
end
It is clear that it depends on YYY module in compile time, but
- when
YYYis changed andrecompile(or justmix) is called,XXXis not recompiled. - when
ZZZis changed and project recompiled,XXXis recompiled, but it is clear thatZZZis not called in compile time
Is this a correct behavior or not?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #ai
- #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
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
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 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
josevalim
Our compile time tracking is based on lexical information and not runtime tracing. So if you hide the module by dynamically generating it, then incremental compilation won’t be applied.
hst337
aliasandrequire asare still tracked thoughRecompiling when
YYYchanged causesXXXto be recompiled too.So, I am guessing that after every macro expansion and unaliasing, compiler just takes all atoms starting with
Elixir.from external context and module body (but not fromdef*) and marks current module dependent from them, right?josevalim
—-
Elixir tracks it during expansion, not after.