tailspin-v0 VS bluebird

I eventually tend to do all days in Tailspin. The ones I have done so far are in directories ending in "tt" (the others are in Pyret, just to get a feel for it) https://github.com/tobega/aoc2023/tree/main

As a general tip, it is often helpful to first try to think of how you would like to represent the data in your program. Then you need to parse the data into that structure. I'd recommend you to look at a PEG-parser, for example. Or if you like, look at my Tailspin programming language which has a very visual parser syntax and also very visual ways of creating data structures (if that should happen to be your mental affinity). Look at my day1 for example. Or if you're more mathematical, maybe a functional language (I also did day1 in Pyret)

My Tailspin language is based on processing streams of values, you might want to look at it https://github.com/tobega/tailspin-v0

Many people had trouble with the day 7 problem. Paradoxically, good developers probably had more trouble. Here some of the difficulties are explained and implementations are provided in imperative, functional and OO styles, written in the Tailspin programming language.

I test almost entirely from my language, that way the tests are independent of the implementation. Currently the tests are implemented in java because that fits the interpreter implementation https://github.com/tobega/tailspin-v0/tree/master/test/tailspin/samples

Finished off the implementation of typed and offset array indices in Tailspin

I ended up enabling left recursion in Tailspin's composer (parser) syntax. Much cleaner calculator example now.

I think it's possible that Tailspin might be suitable for you.

I think gradual typing is definitely something worth exploring more. I thought it was a shame when Dart abandoned that path. Have you seen Shen ? I guess my small offering, Tailspin, is currently evolving to gradual typing as well.

0 upto n and 0 thru n. I think I saw it in Bluebird first and really liked it.

Instead of the classic visitor pattern, I found it easier to create a class that basically wraps a big switch statement that switches on an enum representing the kind of expression. You pass it an expression, and based on the enum returned by its kind() function you downcast the expression into the subclass you need. The code is here for reference. My AST code is here.

I am working some again on my Ada-like language bluebird. I am making another attempt to use MLIR as an intermediate IR between the AST and LLVM IR (I made a brief attempt a few months ago just to look into it).

I fworked some more towards adding pointers on my Ada-like programming language bluebird. I've finished adding pointer types and variables (as well as the operators for dereferencing/getting the address of objects), but I still need to add the ability to dereference and assign.

I started to experiment with using MLIR to write a high-level IR for my language bluebird, which will hopefully reduce the work of implementing features I want to add such as generics and ranges, as well as allowing me to eventually write some optimizations. I am also considering rewriting my AST as an MLIR dialect, since MLIR provides a bunch of type-checking/error printing/support infrastructure.

I continued implementing support for references (a restricted form of pointers) in my Ada-like language bluebird. I also am working on adding a cleanup pass between my parser/typechecker to handle stuff like type resolution of literals and constant folding.

I didn’t add too many new features to my Ada-like language bluebird this month because of lots of projects/school stuff.

Here is a link to my optimizer pass setup for reference. This is just a simple optimization pipeline (I think clang has a setup where optimization stages are re-run multiple times to take advantage of inlining making more optimizations possible).

I made some more progress on bluebird, my Ada-like language.

I continued to make progress on the compiler for my Ada-inspired language bluebird. I will have less time to spend on it as classes began earlier last month, but I still hope to continue working on it. Things are getting to the point where adding a new feature isn’t as difficult as it was when doing so often meant writing the supporting code from nothing.