Does rebar3 load the code it compiles?

We are implementing modules such as application and application_controller (please don’t ask why), but rebar3 will generally crash due to an incomplete (and non-OTP) implementation of these modules.

Does rebar3 (or maybe the Erlang compiler) load modules into the memory|code space of the build tool, when running the compile target?

1 Like

rebar3 does load the code it compiles. I opened a bug about that 2 years ago:

My workaround was to rename one of my modules, but I’m extremely unhappy about that.