Cppfront: Autumn Update

I've always respected choosing 0 as an invalid state. It makes it much harder to accidentally have a function succeed if the default representation is "you messed up"

FTA: In the April blog post, I mentioned I needed a way to write type and namespace aliases, and that because all Cpp2 declarations are of the form thing : type = value, I decided to try using the same syntax but with == to denote “always equal to.”

So, I think we have

  // new type
  foo = std::vector<int>;
  // alias of existing type
  bar == std::vector<int>;

I guess that could evolve to (or maybe already has evolved to?)

  // variable with initial value
  foo: int = 42;
  // constant
  bar: int == 42;

If you start enums at 1, then the first item in the enum isn't coercible to false, all items coerce to true.