# Naming of ScopedValues

**URL:** <https://discourse.julialang.org/t/naming-of-scopedvalues/110747>\
**Category:** Internals & Design\
**Created:** [February 25, 2024, 5:39pm UTC](https://discourse.julialang.org/t/naming-of-scopedvalues/110747 "2024-02-25T17:39:24Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![uniment](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/uniment/32/24532_2.png) [@uniment](https://discourse.julialang.org/u/uniment)\
**Post date:** [March 3, 2024, 6:38pm UTC](https://discourse.julialang.org/t/naming-of-scopedvalues/110747/18 "2024-03-03T18:38:46Z")

</div>

Ah, I see what the problematic use case is: when you want to call a whole stack with a deeply nested dynamically-scoped callee (maybe it’s a low-level routine that relies on a “global”-ish setting, like a numeric tolerance or an iteration depth), but don’t wish to dynamically scope the rest of it.

Nonetheless the point about naming and semantics stands, it’s a wart on the language. These are probably best thought of as “dynamic constants.” Could we have a contextual keyword like `dynamic` for this, as @mnemnion [suggests](https://discourse.julialang.org/t/on-using-vs-for-assignment/110302/73)? Something like this seems far more appealing:

```julia
dynamic const a = 1
f() = a

f() # 1

dynamic let a=2
    f()
end # 2

```

---

_[View the full topic](https://discourse.julialang.org/t/naming-of-scopedvalues/110747)._