TOGVM-Spec
cells
TOGVM-Spec | cells | |
---|---|---|
2 | 6 | |
0 | 208 | |
- | - | |
4.4 | 0.0 | |
10 months ago | over 1 year ago | |
PHP | Common Lisp | |
- | - |
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
cells
-
Spreadsheet Lisp (v0.0.1)
Here is a project that you may be interested in: https://github.com/kennytilton/cells/wiki
-
Interesting examples of visual programming?
For implementation in Common Lisp, I considered using something like Kenny Tilton's Cells.
-
Six programming languages I’d like to see
The reactive programming idea reminded me of Ken Tilton and "Cells", which exploits the flexibility of CLOS (the Common Lisp Object System) to create a reactive programming language on top of Common Lisp.
https://github.com/kennytilton/cells
and he has slides from a talk
https://github.com/kennytilton/cells/blob/main/Lisp-NYC-2018...
to give context.
-
Simple mechanism for CLOS slot dependencies
Nice post. Another way that uses cells.
-
Ask HN: Would Spreadsheets and Lisps be much more powerful?
See Kenny Tilton's Cells project, which more or less does the inverse.
https://github.com/kennytilton/cells
-
😔Non-imaginative person: “So, no choice, I have to keep my logic in my code… There is no other solution…” 😎 Smart person: “Why not create a programming language? 🚀”
I saw Concat without returning a value and got excited that they had reinvented Prolog cause they obviously were going to run Concat backwards, but no, this is bad cells for webshits or something idk
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
om-sharp - OM#: Visual Programming | Computer-assisted Music Compositon
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.
DataLang - Specification and refernce implementation of DataLang
docs - Red-related user documentation repository
power-fx-host-samples - Samples for hosting Power Fx engine.
ODS_OpenExposureData - Open data standards curated by Oasis.