starlight VS konna

I have great news

Hello to all! This crate implements Shadow Stack algorithm which allows to track GC objects on stack with almost zero overhead! This algorithm is used inside Restricted Python and seems to work very well. This crate soon will replace DIY shadow stack implementation in starlight(JS engine in Rust) too.

Working on startup snapshots in starlight. I already have very basic implementation which allows to initialize runtime in just 17 microseconds from snapshot vs 23 microseconds without snapshot when every builtin is created from scratch. Future work is aimed mostly on making deserialization faster

Hi to all! I'm working on starlight (JS engine in Rust) and I can't choose memory management technique: Right now I have conservative on stack precise on heap GC which somehow manages to work but still has segfaults and I'm also working on rcgc feature which will use RC as GC algorithm but my main question: is it worth using RC over tracing cycle and how hard it will be to implement JIT when RC is used? I've never seen any runtimes that use RC and implement JIT.

There's test262_passed file in repo, you can take a look at what tests pass :)

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.