sdk
schmu
sdk | schmu | |
---|---|---|
1 | 3 | |
0 | 24 | |
- | - | |
10.0 | 9.5 | |
over 1 year ago | 6 days ago | |
Python | OCaml | |
- | European Union Public License 1.2 |
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.
sdk
-
November 2022 monthly "What are you working on?" thread
The README contains some instructions on building documentation using cargo (they're not that complete, but we document almost every part of Resurgence at least a little bit), and the SDK repo contains some examples (alongside some RASM code, which is the assembly language we created for development purposes): https://github.com/Resurgence-VM-Development/sdk
schmu
-
November 2022 monthly "What are you working on?" thread
Since the last time I posted, I finished implementing pattern matching for schmu. To make matching on multiple columns less confusing I also added a tuple syntax to the language (finally), which are treated as anonymous records in codegen. Since then, I'm trying to overhaul my memory management, as my RAII-like solution only worked for linear code. In my first big departure from OCaml semantics, I decided to implement mutable value semantics. The paper linked in the Val language introduction makes a strong case for value semantics and after watching a couple of talks by Dave Abrahams, I wanted to try see how it feels. By making mutability be transitive and explicit, it also fixes one of the (few) gripes I have with OCaml that an array can never be really const as it is a reference type (it's possible to enforce constness with modules, but that's not exactly lightweight, syntax wise). Implementing mutable value semantics was pretty straight forward on the typing side, but I'm still not completely done with the codegen. This is due to 1. Assumptions about immutability I made in a lot of places are now wrong, and I had to completely change the way I pass values to functions. 2. I had to implement reference counted arrays, which was more work than I thought it would be. There are still edge-cases coming up in testing from time to time. Yesterday I finally managed it work for tail recursion, yay! I'm looking forward to getting rid of unneeded reference count updates in the future, by moving them to compile time, at least for linear code, lobster style. That's also an excuse to read that Perceus paper again. For the rest of November, I want to enhance my module system a bit. In particular, I want to add signatures and allow locally abstract types. I hope to have this in place before December to do the Advent of Code in my language.
-
September 2022 monthly "What are you working on?" thread
I'm still working on my toy language schmu, an ML-inspired language which uses LLVM as backend.
-
May 2022 monthly "What are you working on?" thread
I spent the time off over the Easter break to write the first program in my language which is not an explicit test and ended up implementing Ray Tracing In One Weekend. It was very rewarding to see how usable the language is already.
What are some alternatives?
edsl - Example of embedding TypeScript as an EDSL inside of another language
Forscape - Scientific computing language
jevkostream.scm - (WIP) Streaming parsers for Jevko in Scheme
vult - Vult is a transcompiler well suited to write high-performance DSP code
community - Features Jevko-related things created by various authors
GLhf - OpenGL Application Abstraction
parsejevko.c - Simple parser for Jevko in C.
peridot - A fast functional language based on two level type theory
parsejevko.java - Simple parser for Jevko in Java.
awesome-low-level-programming-languages - A curated list of low level programming languages (i.e. suitable for OS and game programming)
jevko.lua - A Jevko library for Lua.
Cwerg - The best C-like language that can be implemented in 10kLOC.