# \[ANN\] Pipebraces.jl – piping with braces

**URL:** https://discourse.julialang.org/t/ann-pipebraces-jl-piping-with-braces/93718
**Category:** Package Announcements
**Created:** [January 29, 2023, 1:20am UTC](https://discourse.julialang.org/t/ann-pipebraces-jl-piping-with-braces/93718 "2023-01-29T01:20:04Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [January 29, 2023, 1:55am UTC](https://discourse.julialang.org/t/ann-pipebraces-jl-piping-with-braces/93718/2 "2023-01-29T01:55:13Z")

</div>

If you prefer to use `|>`, with [my implementation](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836) you can already write:

```julia
julia> "a=1 b=2 c=3" |> {
           split
           @. split(it, "=")
           map({Symbol(it[1]) => parse(Int, it[2])}, it)
           NamedTuple
       }
(a = 1, b = 2, c = 3)

```

(although, as previously [explained](https://discourse.julialang.org/t/fixing-the-piping-chaining-issue-rev-3/90836/41), there are reasons to prefer `obj.{...}` over `obj |> {...}`)

What do you believe to be the advantages of this approach over my proposal?

---

_[View the full topic](https://discourse.julialang.org/t/ann-pipebraces-jl-piping-with-braces/93718)._