# Why isn't there a non-! version of deleteat!()?

**URL:** <https://discourse.julialang.org/t/why-isnt-there-a-non-version-of-deleteat/123355>\
**Category:** New to Julia\
**Tags:** abstractvector\
**Created:** [December 2, 2024, 12:50pm UTC](https://discourse.julialang.org/t/why-isnt-there-a-non-version-of-deleteat/123355 "2024-12-02T12:50:17Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![TheLateKronos](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/thelatekronos/32/12824_2.png) [@TheLateKronos](https://discourse.julialang.org/u/TheLateKronos)\
**Post date:** [December 6, 2024, 12:29pm UTC](https://discourse.julialang.org/t/why-isnt-there-a-non-version-of-deleteat/123355/9 "2024-12-06T12:29:41Z")

</div>

In [this thread](https://discourse.julialang.org/t/elegant-way-of-exclusive-indexing/76894/41) i posed a related question, and also arrived at the conclusion that we need a non-mutating version of `deleteat!`. That thread goes into quite a lot of detail showing how users might be tempted to implement this themselves, which to me showcases the “danger” of not providing this functionality out of the box.

While I agree that it is weird to have a non-mutating version of `deleteat!`, just conceptually, there is no argument against it’s usefullness, which I think should come first. Especially given Julia’s strong conventions around using a bang to indicate mutation.

---

_[View the full topic](https://discourse.julialang.org/t/why-isnt-there-a-non-version-of-deleteat/123355)._