There are no problems for you to load in your version of that module again. There is no way to stop anyone from loading in new versions of any module. However there are some properties of code handling you should be aware of:
-
There can at most be 2 versions of a module at the same time, the current and the old. When a new version is loaded in the old version is automatically and irrevocably deleted, the current version becomes the “new” old and the the new one becomes the “new” current.
-
The system doesn’t try and be smart and say that if you already have the version of the module loaded it won’t reloaded It does what you tell it to.
-
The code handling also kills all the processes using the old version of a module when that is deleted.
-
This leads to some fun things. If you reload a module twice you are guaranteed to kill all processes running it regardless of which version they are running.
-
When you call a function in a module which version you call depends on how it is called. If you make a local call you always get the same version while if you make a fully qualified call,
Module.function, you always get a the current version. There is no way to explicitly call functions in the old versions from the “outside”.
Sorry for a quick description of code handling in the BEAM/Erlang/Elixir.
