3 ms·
Doesn't Elixir (and Erlang for that matter) specifically require a module to not be in a specific place in order to have hot reloading of modules? Though I supp
by smj-edison 2y ago
Doesn't Elixir (and Erlang for that matter) specifically require a module to not be in a specific place in order to have hot reloading of modules? Though I suppose you could still have hot reloading and require a module to be in a specific place.
- throwawaymaths 2y agoNope. Elixir doesn't care where your module lives. (You can even "nest" modules, though it's not a great practice)
- __jonas 2y agoNot sure, could be that Elixir stuck close to Erlang's module system yeah. But for example gleam [1] is another language on the BEAM (compiles to Erlang), that has a much nicer approach: All imports must be declared explicitly, and the import path in your local project is based on the file structure so you always know where something is imported from [2]. [1] https://gleam.run/ https://gleam.run/ [2] https://tour.gleam.run/basics/modules/ https://tour.gleam.run/basics/modules/