Cwerg VS konna

Perhaps these have already been dealt with and I'm missing critical information. If so, my apologies. Great work, in any case.

[1] https://github.com/robertmuth/Cwerg/tree/master/FrontEnd#dis...

Cwerg has backend that can be used as JIT and is written with readability in mind. Additional documentation can be found here: https://github.com/robertmuth/Cwerg/tree/master/Docs

I defined a basic ISA-like IR for Cwerg. It has unlimited registers and no constraints on immediates.

entire compiler front end ast nodes

I was also going down the path of bike shedding concrete syntax for my language Cwerg before pulling the plug on that effort and just using s-exprs. I managed to make the s-expr quite succinct by carefully choosing the order of arguments so I can omit optional ones. Also very helpful was to use square brackets for list, e.g. (call fun-name [arg1 arg2]). This simplifies parsing a little bit and is easier on the eye. Here are some Code Examples

I am iterating over the languages features for Cwerg's Frontend which aims to be a low level language with about the complexity of C but with some of the comforts of modern languages. I am especially happy with the choice of adding sum types. Relative to C the current feature set looks like this: Removed: * arrays decay to pointers * bitfields * separate compilation (more of a backend issue) * pre-processor * varargs * implcit type conversions * (untagged) unions * ++/-- * comma operator * implicitly nullable pointers * goto

The second was called Konna. AFAIK it’s Finnish for “frog”, but sources seem to disagree? I don’t speak Finnish, I got the word from a Finnish video game. My third and current language is called Peridot. I’m pretty proud of this name, although it’s less searchable than the previous ones. The origin is pretty simple, I was just looking around at gemstones and thought peridot looked neat.

Continuing work on Konna. I recently finished implementing dependent pattern matching, a pretty big feature! I figured now is the time to do some refactoring and rewriting - the elaborator is the first thing on my list. Once all this maintenance work is done I'll be implementing features like implicit arguments, overloading, and pattern matching on code values.

Github repo: https://github.com/eashanhatti/konna

Continuing work on my functional language Konna. The structured editor has progressed a whole lot recently - the most glaring bugs have been fixed and you can work with the entire language in it. The language itself is going well too, I'm currently thinking through:

Working on a rewrite of Konna (formerly Clamn). After using Rust for a little over a year in the original implementation, I decided I wasn't enjoying it. I'm using Haskell for the rewrite - I'd always wanted to write a big project in Haskell anyway haha. Definitely enjoying the higher-level conveniences it offers. The rewrite has been underway for about two weeks now, and so far I've got basic dependent types and partial evaluation implemented.

Continuing work on my functional systems language Clamn. I'd taken the last few weeks to fix a bunch of performance issues, but now it's finally back to implementing features: record types. I've got dependent types in my lang, which means I can get a bunch of more exciting features for free by implementing records, ADTs for instance.