# Explicit denotation of variability and immutability

**URL:** https://discourse.julialang.org/t/explicit-denotation-of-variability-and-immutability/8686
**Category:** Internals & Design
**Tags:** proposal
**Created:** [January 30, 2018, 10:16am UTC](https://discourse.julialang.org/t/explicit-denotation-of-variability-and-immutability/8686 "2018-01-30T10:16:36Z")
**Posts on this page:** 1
**Showing post:** 27

<div class="post-metadata">

### Author: ![SepandMeenu](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/sepandmeenu/32/8846_2.png) [@SepandMeenu](https://discourse.julialang.org/u/SepandMeenu)
#### Post date: [January 31, 2018, 11:12am UTC](https://discourse.julialang.org/t/explicit-denotation-of-variability-and-immutability/8686/27 "2018-01-31T11:12:30Z")

</div>

Thanks for providing an example. Now I see.  
Yet I deem such a code as _bad_ code, especially for computation.  
Reasoning about what it does is not easy. For example, here, one should first learn about the latest Julia’s conventions on function arguments – which might change – and then understand what `f` would do to an immutable type, or even if the code compiles at all.

I strongly prefer **explicitness** as I said.

---

_[View the full topic](https://discourse.julialang.org/t/explicit-denotation-of-variability-and-immutability/8686)._