# Loops, allocations and helping the coder

**URL:** <https://discourse.julialang.org/t/loops-allocations-and-helping-the-coder/104733>\
**Category:** Internals & Design\
**Created:** [October 8, 2023, 6:18pm UTC](https://discourse.julialang.org/t/loops-allocations-and-helping-the-coder/104733 "2023-10-08T18:18:05Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![nsajko](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nsajko/32/221187_2.png) [@nsajko](https://discourse.julialang.org/u/nsajko)\
**Post date:** [October 8, 2023, 7:25pm UTC](https://discourse.julialang.org/t/loops-allocations-and-helping-the-coder/104733/5 "2023-10-08T19:25:27Z")

</div>

> [@Paul\_Soderlind](#):
>
> Therefore, my question: could “compiler” development possibly help the users with this?

[This](https://discourse.julialang.org/t/option-to-completely-disallow-dynamic-allocation/1417) seems like one possible feature that could help, in addition to the already existing features like the allocation profilers.

---

_[View the full topic](https://discourse.julialang.org/t/loops-allocations-and-helping-the-coder/104733)._