TOGVM-Spec
power-fx-host-samples
TOGVM-Spec | power-fx-host-samples | |
---|---|---|
2 | 1 | |
0 | 122 | |
- | 0.8% | |
4.4 | 5.7 | |
9 months ago | 5 months ago | |
PHP | ||
- | MIT License |
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
power-fx-host-samples
-
Six programming languages I’d like to see
OP's Excel example made me think of Power Fx and the Power Fx Host
https://powerapps.microsoft.com/en-us/blog/power-fx-open-sou...
https://github.com/microsoft/power-fx-host-samples/tree/main...
What are some alternatives?
impulse - Impossible Dev Tools for React and Tailwind
letlang - Functional language with a powerful type system.
dafny - Dafny is a verification-aware programming language
inform - The core software distribution for the Inform 7 programming language.
sdk - The Dart SDK, including the VM, dart2js, core libraries, and more.
Lazy - Lazily evaluated (late-binding) definition for Dyalog APL
prusti-dev - A static verifier for Rust, based on the Viper verification infrastructure.
magrittr - Improve the readability of R code with the pipe
docs - Red-related user documentation repository
ODS_OpenExposureData - Open data standards curated by Oasis.
DataLang - Specification and refernce implementation of DataLang
scenebuilder - Scene Builder is a visual, drag 'n' drop, layout tool for designing JavaFX application user interfaces.