# 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:** 10

<div class="post-metadata">

**Author:** ![DNF](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/dnf/32/10191_2.png) [@DNF](https://discourse.julialang.org/u/DNF)\
**Post date:** [June 9, 2021, 9:44pm UTC](https://discourse.julialang.org/t/implicitly-loaded-modules-in-the-future/62646/10 "2021-06-09T21:44:54Z")

</div>

It seems that the issues you raise were addressed in this thread

> [@Julia Modules](https://discourse.julialang.org/t/julia-modules/7028):
>
> The current situation with Julia modules is a nightmare with various keywords (include, using, import) and a lack of a simple and standard system for the compiler to find modules without playing around with source files. The same goes for exports. Rust has a nice and clean system of addressing these issues. Are there any plans for version 1.0 or beyond to provide a solution for this problem?

that you opened some years ago. There doesn’t seem to be any new complaints in this iteration.

Was the advice in that thread not helpful?

---

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