PaddedViews.jl VS Chain.jl

As sibling posts have pointed out, you can in fact do all of those things:

1. You can write a getproperty method for a tuple. It is considered to be type piracy and thus runs the risk of colliding with someone else's definition, but the language absolutely lets you do it.

2. You can broadcast over the fields of a NamedTuple by defining appropriate methods. Again, it's type piracy, so take that into consideration but the language lets you do this easily.

3. The https://github.com/JuliaArrays/PaddedViews.jl package implements exactly what you're saying Julia won't let you do.

If anything, Julia errs on the side of allowing you to do too many things! There are very few things the language says really won't let you do.

For the last thing, is this what you want? https://github.com/JuliaArrays/PaddedViews.jl

There may be other packages or

The [Chain.jl package](https://github.com/jkrumbiegel/Chain.jl) is becoming idiomatic for these kind of pipelines.

If you do have tabular data in a dataframe you have a few options for data manipulation, the most popular packages are probably DataFramesMeta and Query, although in my opinion the best way to manipulate dataframes is with the functions built in to DataFrames.jl and using a package like Chain.jl or Pipe.jl to pipe the functions into each other like magrittr in R.

@chain and @match.

Have you ever tried Infiltrator.jl and Chain.jl?

I never noticed that Julia's pipe wasn't considered idiomatic. Actually, not only a lot of people use pipes, but Julia also has one of the best pipes ever with Chain.jl.

I also like pipe syntax and I've found there is nice support for it in Julia. There are some nice packages to improve it over base [1].

Have you checked queryverse [2]?

[1] https://github.com/jkrumbiegel/Chain.jl