# Fixing the Piping/Chaining Issue (Rev 3)

**URL:** <https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836>\
**Category:** Internals & Design\
**Tags:** multithreading, syntax, piping, chaining, threading\
**Created:** [November 26, 2022, 2:50am UTC](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836 "2022-11-26T02:50:46Z")\
**Posts on this page:** 1\
**Showing post:** 25

<div class="post-metadata">

**Author:** ![uniment](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/uniment/32/24532_2.png) [@uniment](https://discourse.julialang.org/u/uniment)\
**Post date:** [December 2, 2022, 8:07pm UTC](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836/25 "2022-12-02T20:07:11Z")

</div>

> [@Sukera](#):
>
> we have a powerful, proper macro system that can accommodate all of them, even without changing the core language - hence, there is much less need to add one controversial thing.

This is both a blessing and a curse. As has been discussed ad nauseam in [this thread](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue/89654) and summarized in the OP of [this thread](https://discourse.julialang.org/t/fixing-the-piping-chaining-partial-application-issue-rev-2/90408/), there are compelling benefits to choosing a single, officially-ordained approach for method chaining. It is, of course, fine for other approaches to exist too, as will occur when a domain-specific case justifies it.

---

_[View the full topic](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836)._