Single module vs. submodules in a project

[MA_Laforge]

@erans

Thanks for all the tips, regarding this specific point though, my main interest currently is the best way to structure code. My thought was, that the “best” way would likely best leverage Julia’s capabilities. As far as I can tell, the two main Julia highlights are JIT and multiple dispatch. With that in mind, I was/am trying to figure out how my code structure can best play nice with these concepts.

If that’s the case, I suggest you take a look at my post here (and those it links to):

How to load a module from the current directory?

I don’t think this particular behaviour is documented yet. If it is, it wasn’t visible enough for me to find it: I as well struggled with this issue a few months ago. The confusion In particular, I had to look through Julia’s code to understand that any entry in LOAD_PATH, whose directory contains a Project.toml file, will be treated as a “project environment” only. In other words: having a Project.toml file inhibits Julia from using it as a “package repository”. An introduction, for now At …