# Implicitly loaded modules in the future?

**URL:** <https://discourse.julialang.org/t/implicitly-loaded-modules-in-the-future/62646>\
**Category:** Internals & Design\
**Tags:** question, module, code-organization\
**Created:** [June 9, 2021, 8:58pm UTC](https://discourse.julialang.org/t/implicitly-loaded-modules-in-the-future/62646 "2021-06-09T20:58:00Z")\
**Posts on this page:** 1\
**Showing post:** 111

<div class="post-metadata">

**Author:** ![lmiq](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lmiq/32/18314_2.png) [@lmiq](https://discourse.julialang.org/u/lmiq)\
**Post date:** [June 12, 2021, 7:58pm UTC](https://discourse.julialang.org/t/implicitly-loaded-modules-in-the-future/62646/111 "2021-06-12T19:58:36Z")

</div>

> [@jonathan-laurent](#):
>
> _dividing a package into a lot of small, lowly-coupled semantic units with local definitions and a clear dependency graph_

If we could (edit: we can 🙂) do this I posted in this other thread, at the cost of having a “directory-\>module” correspondence and a Project.toml file for each module, that could be achieved without any new language feature (and from what I see adding the benefit of expanding the possible uses of each module beyond the limited scope of one package:

> [@(not to be taken seriously) ideas about modules and packages](https://discourse.julialang.org/t/not-to-be-taken-seriously-ideas-about-modules-and-packages/62672/6):
>
> I am not sure if almost that is already possible, in fact. If we have a package with a directory structure like: MyPackage --- Project.toml --- src --- MyPackageUtils ------Project.toml ------src ----MyPackageExamples -------Project.toml -------src Can we register the three packages there independently in the general registry? Can two different packages point to different directories of the same GitHub repository? And, of course, have the these packages dependent on each other (I don’t mean ci…

---

_[View the full topic](https://discourse.julialang.org/t/implicitly-loaded-modules-in-the-future/62646)._
