# bang await chaining operator

**URL:** <https://es.discourse.group/t/bang-await-chaining-operator/940>\
**Category:** 💡 Ideas\
**Tags:** proposal\
**Created:** [August 21, 2021, 10:22pm UTC](https://es.discourse.group/t/bang-await-chaining-operator/940 "2021-08-21T22:22:47Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mhofman](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mhofman](https://es.discourse.group/u/mhofman)\
**Post date:** [January 13, 2023, 4:52pm UTC](https://es.discourse.group/t/bang-await-chaining-operator/940/7 "2023-01-13T16:52:18Z")

</div>

As I explained in [Async property accessor: -\> - #5 by mhofman](https://es.discourse.group/t/async-property-accessor/765/5), wavy dot is meant to enable avoiding intermediary `await`, allowing to pipeline the operations when they are performed on a remote system.

If operations execute in a single JS agent, then there is no difference with explicit awaiting, and the eventual-send effectively does that since the promise is decided locally.

The pipeline operator may help tidying the nested aspect without a new dedicated operator:

```javascript
const posts = await fetch('/posts') |> await %.json();

```

---

_[View the full topic](https://es.discourse.group/t/bang-await-chaining-operator/940)._