magrittr VS roast

R (yes, the statistics language) has exactly this.

You can literally extract the body of a function as a list of "call" objects (which are themselves just dressed-up lists of symbols), inject/delete/modify individual statements, and then re-cast your new list to a new function object.

I don't know why the original devs thought this was necessary or even desirable in a statistics package, but it turns out to be a lot of fun to program with. It has also made possible a wide variety of clever and elegant custom syntaxes, such as a pipe infix operator implemented as a 3rd-party library without any custom language extensions [0]. The pipe infix operator got so popular that it was eventually made part of the language core syntax in version 4.1 [1].

[0]: https://magrittr.tidyverse.org/

[1]: https://www.r-bloggers.com/2021/05/the-new-r-pipe/

In R (thanks to magrittr) you can now perform operations with a more functional piping syntax via %>%. This means that instead of coding this:

Try reading the documentation for magrittr.

Related note: the statistical programming language R has a library named magrittr to support the pipe operator.

About the pipe (%>%) symbol, it's provided by the magrittr package. The package documentation details how to use the pipe operator.

I was wondering what some good ways are to handle nested function calls without chaining them in long, ugly nested statements. I am looking for functionality similar to the pipe forward operator %>% in magrittr/R or |> in F#.

You may like R: https://magrittr.tidyverse.org

Agreed on everything else you said (especially the type safety stuff, it massively helps in production), but one correction: magrittr is absolutely in the tidyverse suite. It's not considered one of its "core" packages that it visibly tells you it loads, but magrittr is loaded when calling library(tidyverse) and development of the package is handled by the tidyverse team under their Github account: https://github.com/tidyverse/magrittr

The Raku programming language has, with some tweaks:

data.store.book.grep(.price < 10).map(.title)

Although personally I would write that as:

data.store.book.map: { .title if .price < 10 }

which combines the filter / map into a single operation.

https://raku.org

Add more IO::Path::parent tests #801: merged 2022-02-19

23. Raku - $79,448

Pakku is a package manager for the Raku Programming Language. Latest releases of Pakku are part of Pakku Celastrina version family. Celastrina name means elegant and beutiful, So I will take the opportunity to introduce how elegant IMO Pakku handles Raku distributions.

At the last European Perl Conference I proposed to change the name of "Perl 6". After a lot of discussion, it was decided that it was going to be called the Raku Programming Language.

Raku note: This language has no length method on strings, because in Unicode world it is super confusing. Instead there are separate methods to ask precisely about amount of characters, amount of code points and amount of bytes.

Elizabeth Mattijsen reports on all recent developments around Rakudo, an implementation of the Raku Programming Language.

The raku.org website.