xvm VS list-exp

Parts of Ecstasy are now implemented in Ecstasy. Here's the Lexer, for example.

Ecstasy

A Future reference has the various capabilities that you'd imagine, taking lambdas for thenDo(), whenComplete(), etc. The reference, in the above example, is a local variable, so you just obtain it using the C-style & operator:

FWIW - here is the stage manager code that I referred to.

Ecstasy (xtclang.org): Currently working on session management for a cloud-based HTTP back end. Not exactly compiler or language stuff, but it certainly is exercising the compiler and language.

I prefer to make my AST nodes fairly rich, and let them do the brunt of the work themselves. Instead of the 5 lines of code above, the assignment statement node in Ecstasy is over 1000 LOC. But it handles everything from initial validation through the MLIR emission.

No, not that specific project. It's our own Mid Level Intermediate Representation (or Mid Level Intermediate Language), aka MLIR/MLIL. Here's a snapshot of the operators.

Ecstasy project on Github: https://github.com/xtclang/xvm

Quite a few improvements in Ecstasy over the past month:

Early on, we had the This keyword, and its meaning was "this type". So if a method on class Collection was declared as This add(Element), it meant that the method returned the auto-narrowing type of this. We later changed it from This to Collection (or whatever the class name is) and added the Collection! (non-narrowing) form, because there were syntactic needs (e.g. inner and outer auto-narrowing class references) that could not be covered by This. We evaluated a few different options, and we liked (and still like) the result that we came up with. That said, I still wish we had a This keyword (see the 5th bullet point) for the "this type", but 🤷‍♂️.

I've been playing around with regex-like syntax for list operations in list-exp. Not a particularly useful thing but it was really fun to implement. Working on replaceAll function now which will work as a filter-map operation.