TOGVM-Spec
magrittr
TOGVM-Spec | magrittr | |
---|---|---|
2 | 10 | |
0 | 951 | |
- | 0.0% | |
4.4 | 2.3 | |
9 months ago | about 1 year ago | |
PHP | 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.
TOGVM-Spec
-
The AST Typing Problem
Make each AST node an RDF node and then you can cram whatever information into it you want. That's the approach I've been taking with https://github.com/TOGoS/TOGVM-Spec/, anyway.
Of course, for conveniently and safely manipulating in memory in $programming_language, you're probably going to want to define some structs/ADTs/whatever that only contain the data a given compilation stage is actively working with.
I've been thinking that what I need is a system that allows me to quickly define different lower-level datatypes for representing different views of the conceptual types and automate, to some degree, translation between them, so then each part of the system can work with objects designed specifically to be processed by it with minimal fuss.
A technical reason for avoiding those specialized types might be that the computer then has to spend more time transforming from one schema to the next. I would think that in practice this isn't any worse than having to do a lot of null checks.
A more human reason is that it could bean a combinatorical explosion of AST types. I guess this is where my idea about lightweight variations comes in.
In TypeScript this kind of thing might not be so bad, since any object can be downcast with no cost to a type that contains a subset of the information, and variations on types can be easily defined without even necessarily being named, e.g. `ASTNode & HasResultType & HasSourceLocation`.
-
Six programming languages I’d like to see
As far as graph-based languages and languages with arbitrary metadata and relationships between objects are concerned, I've been mulling over a language where expressions are represented as RDF graphs and that has built-in support for manipulating RDF graphs. I've use the concepts as an intermediate representation for functional expressions in a few different systems (including Factorio's map generator), but haven't yet had the motivation to really flesh it out into a full-blown language. https://github.com/TOGoS/TOGVM-Spec
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?
impulse - Impossible Dev Tools for React and Tailwind
dplyr - dplyr: A grammar of data manipulation
dafny - Dafny is a verification-aware programming language
scenebuilder - Scene Builder is a visual, drag 'n' drop, layout tool for designing JavaFX application user interfaces.
sdk - The Dart SDK, including the VM, dart2js, core libraries, and more.
kitten - A statically typed concatenative systems programming language.
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
power-fx-host-samples - Samples for hosting Power Fx engine.
docs - Red-related user documentation repository
libuv-tutorial - http://nikhilm.github.io/uvbook/
DataLang - Specification and refernce implementation of DataLang
ggplot2 - An implementation of the Grammar of Graphics in R