# @async macro not recommended?

**URL:** https://discourse.julialang.org/t/async-macro-not-recommended/112404
**Category:** General Usage
**Created:** [April 2, 2024, 8:33am UTC](https://discourse.julialang.org/t/async-macro-not-recommended/112404 "2024-04-02T08:33:33Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![phantom](https://avatars.discourse-cdn.com/v4/letter/p/e0b2c6/32.png) [@phantom](https://discourse.julialang.org/u/phantom)
#### Post date: [April 3, 2024, 5:39am UTC](https://discourse.julialang.org/t/async-macro-not-recommended/112404/5 "2024-04-03T05:39:33Z")

</div>

So are there cases where `@async` would still be preferred over `@spawn` in order to avoid race conditions? E.g. if you have a parallel mutations of arrays that aren’t thread safe as noted by stevengj [here](https://discourse.julialang.org/t/best-data-structure-for-recursive-functions/112289). Sorry i’m still a little confused about this point.

---

_[View the full topic](https://discourse.julialang.org/t/async-macro-not-recommended/112404)._