# @sync block drops asynchronous errors in favor of synchronous errors

**URL:** <https://discourse.julialang.org/t/sync-block-drops-asynchronous-errors-in-favor-of-synchronous-errors/26440>\
**Category:** Internals & Design\
**Created:** [July 16, 2019, 8:53pm UTC](https://discourse.julialang.org/t/sync-block-drops-asynchronous-errors-in-favor-of-synchronous-errors/26440 "2019-07-16T20:53:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Jasha10](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jasha10/32/7508_2.png) [@Jasha10](https://discourse.julialang.org/u/Jasha10)\
**Post date:** [July 17, 2019, 7:25am UTC](https://discourse.julialang.org/t/sync-block-drops-asynchronous-errors-in-favor-of-synchronous-errors/26440/3 "2019-07-17T07:25:04Z")

</div>

I’ve realized that this topic is actually related to the discussions about structured concurrency a la nurseries.  
E.g [@schedule considered harmful](https://discourse.julialang.org/t/schedule-considered-harmful/10540)

---

_[View the full topic](https://discourse.julialang.org/t/sync-block-drops-asynchronous-errors-in-favor-of-synchronous-errors/26440)._