Forscape VS boba

And if you like mathematical languages, you should check out Forscape :)

You can use the free GitHub runners to execute regression tests on Linux, Windows, and Mac. I recommend testing with 32bit compilation as well as 64bit- it has a way of smoking out bugs. You could take a look at the GitHub actions on my Forscape repo in the .github folder, although it's probably not the most idiomatic runner scripting, but it is a C++ project like yours.

When I was developing a typesetting text editor for Forscape, I struggled to get traction until stumbling on the following plan: 1) Implement the document data structure and get it rendering to the screen 2) Support non-mutating interactions, such as clicking to move the text cursor, selecting, copying, etcetera 3) Support mutating interactions, such as keyboard input, deleting, and pasting. You'll probably use the Command pattern to support undo/redo of mutations

The project is Forscape, although the language part is made a bit complicated because a goal of the project is creating an editor that supports typeset code with IDE interaction

Finally adding multi-file support to Forscape. The frontend UI aspects are completed and I'm quite happy with the result. The app is Unicode heavy and QString's UTF-16 encoding is an annoyance; I would much prefer if Qt relied on std::string even. But the signal/slot mechanism lets you achieve some complicated behaviour with minimal complexity, and Qt looks great.

Here's an example from a project. The first step installs Qt, the second step clones my repo on the runner, then a bit more setup with Conan, then building and running.

I've been working on the Key CAS project (Imgur Screenshot), CAS being an acronym for Computer Algebra System, and "Key" a judiciously chosen title. This was my third time attempting CAS- this iteration was a huge improvement, but I still find it to be a damn hard problem. The GUI comes from the open source project Forscape, a scientific computing environment written in C++.

It gets fun when you go beyond flat symbols and start supporting 2D notation, like fractions and matrices. Probably not worth the hassle for most things, but I think it makes matrix expressions more compact with better readability.

I've been working on a mathematical programming language, Forscape. Currently it's entirely numerical, but I'm building a CAS separately which I hope to use in the language.

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.