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
Build Elixir applications with speed and confidence.
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
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
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.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 3 of 3 Posts
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.