dplyr VS magrittr

That's great feedback, thanks!

This tool definitely comes from a place of personal need - beyond just handling large files, I've also never really gelled well with the Excel/Google Sheet model of changing data in place as if you were editing text. I'm a Data Scientist and always preferred the chained data transforms you see in things like dplyr (https://dplyr.tidyverse.org/) or Polars (https://pola.rs/) and I feel this tool maps very closely to the chained model.

Also, thank you for the feature requests! Those would all be very useful - we'll put them on the roadmap.

There's an example of how to use zzz.R with a .onload() function to set options in the dplyr code base: https://github.com/tidyverse/dplyr/blob/bbcfe99e29fe737d456b0d7adc33d3c445a32d9d/R/zzz.r

Look at the tidyverse, especially the case_when or mutate functions.

Before diving into advanced machine learning algorithms or statistical models, we need to start with the basics: collecting and organizing data. Fortunately, both Python and R offer a wealth of libraries that make it easy to collect data from a variety of sources, including web scraping, APIs, and reading from files. Key libraries in Python include requests, BeautifulSoup, and pandas, while R has httr, rvest, and dplyr.

It looks like your syntax is wrong. I think you’re trying to calculate a new variables in your data frame, or alter an existing column in a data frame. Have a look at the select() function in this reference for the proper syntax to use. https://dplyr.tidyverse.org/ Does that help?

A lot of populat libraries have their own logos. Maybe one of them would be good. Check out dplyr for example: https://dplyr.tidyverse.org/

I hope you give it a try when you get a chance: https://dplyr.tidyverse.org/

You can read up on the dplyr-verbs here, which I strongly suggest for your exam! In the code examples, you can simply click on any function you don't understand and it will take you directly to the documentation. Good Luck!

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