boba VS kuroko

I've done a small implementation, used in type inference, in my language Boba. And you are correct, I used the linear equation solving method.

The vast majority of October's improvements on Boba were type system and runtime bug fixes. In particular, the effect handler/delimited continuation semantics were hopelessly busted beyond a few simple examples I'd fixated on.

September was another productive month for Boba, which is starting to get more 'quality of life' improvements rather than broad new features. That doesn't make the work less important: one of the bug fixes to the type inference engine last month caught a previously unseen bug in the core Boba libraries!

Also worth checking out is Adam Gundry's work on type inference for UoM types. Or, if you want an example implementation of the Abelian unification used in standard type inference extended with UoM types, you can reference my implementation, based on solving linear equations.

August was a surprisingly productive month for the Boba compiler. A few highlights:

The next large feature for Boba (a general-purpose concatenative language) is language integrated property tests.

That's a good question! I wrote up some of my thoughts on the benefits of Go as a backend, but there's also a historical component here. The first backend I was experimenting with was compile-to-C plus a C-based runtime. Go was closer to C than C# for what I needed at the time and I thought had a nicer concurrency story as a backend.

(kuroko)[https://github.com/kuroko-lang/kuroko] is basically Python, but C

Kuroko: Dialect of Python with explicit variable declaration and block scoping, with a lightweight and easy-to-embed bytecode compiler and interpreter.

I would say Kuroko makes more sense ;-P

Kuroko 1.3.0 gets a release candidate. Lots of big things since 1.2.5, like optimized method invocation, more operator overloads, better support for f-string expressions (format specs, =, faster constructions), a long type with my own bigint implementation (this was the last thing I was still regularly opening Python repls for, so a huge personal win). I also fixed a bunch of little things that have been nagging me, like the compiler can now compile expressions directly, which allowed me to remove the kludge that made the repl work previously. The WASM web repl also got some love with a port of the core of Hiwire from Pyodide, giving a very straightforward interface between JS and Kuroko in a browser - and I rebuilt the web IDE on it. I've also been working on a new compiler, which will hopefully form the basis of 2.0 - and this might be the last 1.x release (though I expect at least a few 1.3.x bug fix releases).

In case it's not clear, PonyOS is a joke reskin of my serious OS project, ToaruOS. PonyOS gets a new release every April 1st. All of the libraries and applications in ToaruOS are in-house things I built myself - the whole OS is "built from scratch". PonyOS adds ponysay, which is an external app originally written in Python - and in previous releases of PonyOS I shipped the Python version alongside a port of Python 3.6. This release, though, comes with a port to my own language, Kuroko, which is a dialect of Python - a lot of what went into building the PonyOS release this year was getting ponysay to work well.

Did this year's Advent of Code in Kuroko which sussed out some bugs and missing functionality. Better hashing for tuples, more builtins and methods on standard classes for improved compatibility with Python, general build cleanups. In the later problems, most suffering was caused by the GC, so I'd like to put more thought into collection strategies going forward.

Is it me you're looking for?