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

<div class="post-metadata">

**Author:** ![jeff.bezanson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jeff.bezanson/32/48_2.png) [@jeff.bezanson](https://discourse.julialang.org/u/jeff.bezanson)\
**Post date:** [January 29, 2019, 10:48pm UTC](https://discourse.julialang.org/t/new-scope-solution/16707/223 "2019-01-29T22:48:44Z")

</div>

I might, in fact, change my mind… The problem is that

1. @tim.holy points out that it is useful to have a top-level construct where code inside it works just like a function body.
2. Nobody really has a problem with how `let` works currently; loops are the only issue.

So we might need to be open to handling loops differently.

---

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