Carl Mäsak

An intriguing suggestion. Alma is on hiatus right now as I work on [that other thing](https://github.com/masak/bel), and packaging up Alma in order to expose it to a place like TIO,...

> - `constant` declarations might be OK, though. They'd be a kind of once-only variables, valid throughout the class. If we wanted to be fancy, we could even allow `MyClass.someConstant`...

> - As a consequence, there's no private state. You can't even emulate it by having the methods close over a lexical defined outside of the class. (Or you _could_,...

It's funny, we use the `{}` constructor syntax to create objects that are like records, and the `()` syntax to create tuple-like objects. It's quite clear what the `[]` constructor...

Another issue not addressed yet: subtype relations. I'm a bit hesitant with this one, because I think class inheritance tends to be abused much of the time to shunt methods...

> Array-like types! As I'm using this in practice, it becomes clear that this is a general phenomenon where I just saw the specific case of the array until now....

> The common denominator is not a single array attribute, but a single attribute, period. And yes — in practice this gives us Ven++'s `newtype` functionality. Single-attribute types are simply...

> A class `S` is a subtype of a class `T` (`S

> Maybe the thing we should keep is that a class that declares itself a subtype must also declare all the attributes of its supertype. And all the methods, presumably....

> It strikes me that I would also be OK with the convention being that the sole attribute be called `value`, a bit like in Java annotations. Not to mention...