docs
magrittr
docs | magrittr | |
---|---|---|
4 | 10 | |
58 | 951 | |
- | 0.0% | |
6.2 | 2.3 | |
about 2 months ago | about 1 year ago | |
CSS | R | |
- | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
Six programming languages I’d like to see
The interesting semantic relationships are those that let the machine automatically deduce optimizations
> I also like the idea of modifying function definitions at runtime. I have these visions/nightmares of programs that take other programs as input and then let me run experiments on how the program behaves under certain changes to the source code. I want to write metaprograms dammit
Lotta metaprogramming in Joy. Many functions work by building new functions and running them, it's a natural idiom in Joy.
- - - -
> A language designed around having first-class GUI support
Red? ( https://www.red-lang.org/ )
> Visual Interface Dialect ... is a dialect of Red, providing the simplest possible way to specify graphic components with their properties, layouts and even event handlers. VID code is compiled at runtime to a tree of faces suitable for displaying.
https://github.com/red/docs/blob/master/en/gui.adoc
> You can’t work with strings, json, sets, or hash maps very well, date manipulation is terrible, you can barely do combinatorics problems, etc etc etc. I want a language that’s terse for everything.
That also sounds like Red.
-
Beads: The next generation computer language and toolchain
> They are well funded.
Rebol Technologies went bankrupt, and Rebol is de-facto dead since more than a decade; Red barely manages to get by thanks to a recent crypto spike.
> I would say the languages are very different in the sense that Beads is clearly aimed at graphical interactive software.
So is Red with it's native GUI engine. [1]
> They are so different that it is hard to compare.
Both share the same goal of replacing modern software practices with biased, batteries-included toolchain, varying only in implementation.
> Red being a concatenative language has more in common with FORTH than Algol.
Red is not concatenative in any sense of the word, nor any other language in Rebol family that I know of.
[1]: https://github.com/red/docs/blob/master/en/view.adoc
-
One Way to Represent Things
> What if a simpler programming language had first-class representations of a lot more than strings and arrays?
Red lang?
> Where most languages have 6-8 base datatypes, Red has almost 50.
https://github.com/red/docs/blob/master/en/datatypes.adoc
magrittr
- This is not a pipe - René Magritte
-
Six programming languages I’d like to see
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/
- Hadley is pro- base pipe.
-
Functional pipes in python like %>% from R's magrittr
In R (thanks to magrittr) you can now perform operations with a more functional piping syntax via %>%. This means that instead of coding this:
-
Question about dot notation
Try reading the documentation for magrittr.
-
When did WG21 decide this is what networking looks like?
Related note: the statistical programming language R has a library named magrittr to support the pipe operator.
-
How can I find the data entry of the row after one found?
About the pipe (%>%) symbol, it's provided by the magrittr package. The package documentation details how to use the pipe operator.
-
Best practice for chaining nested functions?
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#.
-
I much prefer `data.action()` to `action(data). Is it an r/unpopularopinion?
You may like R: https://magrittr.tidyverse.org
-
What's so "tidy" about tidyverse?
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
What are some alternatives?
beads-examples - Examples of Beads programs
dplyr - dplyr: A grammar of data manipulation
power-fx-host-samples - Samples for hosting Power Fx engine.
scenebuilder - Scene Builder is a visual, drag 'n' drop, layout tool for designing JavaFX application user interfaces.
ODS_OpenExposureData - Open data standards curated by Oasis.
kitten - A statically typed concatenative systems programming language.
letlang - Functional language with a powerful type system.
Graal - GraalVM compiles Java applications into native executables that start instantly, scale fast, and use fewer compute resources 🚀
libuv-tutorial - http://nikhilm.github.io/uvbook/
Lazy - Lazily evaluated (late-binding) definition for Dyalog APL
ggplot2 - An implementation of the Grammar of Graphics in R