# Another possible solution to the global scope debacle

**URL:** <https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894>\
**Category:** Internals & Design\
**Created:** [October 4, 2018, 6:14pm UTC](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894 "2018-10-04T18:14:07Z")\
**Posts on this page:** 1\
**Showing post:** 235

<div class="post-metadata">

**Author:** ![mbauman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mbauman/32/31082_2.png) [@mbauman](https://discourse.julialang.org/u/mbauman)\
**Post date:** [November 6, 2018, 3:54pm UTC](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894/235 "2018-11-06T15:54:01Z")

</div>

Let’s try to keep the conversations around this topic organized — the latest discussion is happening in the [New scope solution](https://discourse.julialang.org/t/new-scope-solution/16707) thread. I’m going to close this topic in favor of that one.

---

_[View the full topic](https://discourse.julialang.org/t/another-possible-solution-to-the-global-scope-debacle/15894)._