# New scope solution

**URL:** <https://discourse.julialang.org/t/new-scope-solution/16707>\
**Category:** Internals & Design\
**Tags:** proposal\
**Created:** [October 23, 2018, 8:58pm UTC](https://discourse.julialang.org/t/new-scope-solution/16707 "2018-10-23T20:58:16Z")\
**Posts on this page:** 1\
**Showing post:** 168

<div class="post-metadata">

**Author:** ![Azamat](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/azamat/32/6892_2.png) [@Azamat](https://discourse.julialang.org/u/Azamat)\
**Post date:** [January 28, 2019, 12:20am UTC](https://discourse.julialang.org/t/new-scope-solution/16707/168 "2019-01-28T00:20:37Z")

</div>

I also come to like the current behavior of loops for the reasons outlined by @StefanKarpinski [here](https://discourse.julialang.org/t/global-scope-confusion-again/20044/46)

Maybe we can crowdfund the GUI debugger feature if that will accelerate its arrival. I’m sure it will have popular support as I can see from this issue that there is a high demand for it.

---

_[View the full topic](https://discourse.julialang.org/t/new-scope-solution/16707)._