hatsugen
pattern-matching-in-rust
hatsugen | pattern-matching-in-rust | |
---|---|---|
3 | 4 | |
5 | 191 | |
- | - | |
2.1 | 5.0 | |
about 1 year ago | 3 months ago | |
Lean | Rust | |
MIT License | The Unlicense |
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.
hatsugen
-
A decade of developing a programming language
Might this help? I wrote it: https://azdavis.net/posts/define-pl-01/
-
Rust in 2023 - azdavis
Perhaps my own series of posts? It starts here.
-
Memories: Edinburgh ML to Standard ML
2. Preservation states that if you have a program that type-checks _and_ that can continue evaluating, _as_ it continues to evaluate, it _continues_ to type-check.
Note that the conclusion of preservation 'feeds back' into progress: the program type-checks. And vice versa: progress may state as its conclusion that the program can continue evaluating, which then lets you apply preservation. This means you can keep applying the progress and preservation theorems in a 'loop' until the program is done evaluating.
For each of the 4 posts in my series about formal semantics, I duly translated the rules presented in the blog post into Lean code, and then proved that the rules do satisfy the safety properties. For example, for the first post linked above:
- The syntax of the language: https://github.com/azdavis/hatsugen/blob/part-01/src/syntax....
pattern-matching-in-rust
- Pattern matching and exhaustiveness checking algorithms implemented in Rust
- Pattern Matching in Rust
-
A decade of developing a programming language
I'm planning on doing something similar to what I did for pattern matching [1]: basically building something entirely standalone that fits in 2k LOC or so, and explains the basics (i.e. nominal typing plus basic sub-typing), hopefully such that people can then take that and extend it.
As for _when_ I'll do that, that depends on when I can convince my inner critic to actually commit to the idea :)
[1]: https://github.com/yorickpeterse/pattern-matching-in-rust
What are some alternatives?
pkg - Package your Node.js project into an executable
boreal - Safe and performant YARA rules evaluator
rust - Empowering everyone to build reliable and efficient software.
sml-buildscripts - Scripts to compile and run Standard ML programs defined in .mlb files.
hm - a simple Hindley-Milner type system in Go
fyg-lang - Fyg is a simple high-level, functional-imperative with runtime type safety for the aspiring grug
cool_asserts - Some useful assertions for Rust
swc - Rust-based platform for the Web
example - Go example projects