Joe Eli McIlvain

It looks like this is at least partially complete with #1058, but it's currently an optional process that takes extra work on the user-developer side to make it happen, rather...

It looks like the next logical step is make it so that the `libponyrt` bitcode gets built for ponyc releases, and bundled with the distribution of `ponyc` binaries, just like...

If anyone is curious about the code I'm compiling, here it is: https://github.com/jemc/pony-ast/blob/85f3ad7ec1a9fd2154ff2b759098b1f19238cddc/static/ast.pony Note that the code is generated, not hand-written. The definitions that it is generated from are here:...

The extra flattening seems to be due in large part to the way type aliases are eliminated in the `names` pass, just before the `flatten` pass. That is, in the...

@sylvanc - Just to be clear, which parts of flattening do we want to eliminate? Get rid of just union flattening? Get rid of union and intersection flattening? Get rid...

As discussed on the sync call, @sylvanc was referring to getting rid of union flattening, not the entire `flatten` pass. Another alternative would be to keep the structural flattening of...

I've opened PR #1723 to implement one of the improvements mentioned above: > keep the structural flattening of unions (going from a node with N-1 nested levels of children to...

> But if the check happens before the reification, there's no way to safely decide at compile time. Should this check be done without reification of the specific instantiation? Part...

For whoever is interested in doing this - this will require expanding the parser to allow the invalid syntax, then checking for and disallowing the invalid syntax during the `syntax.c`...

Reclassified. @Praetonus can you elaborate on the "non-negligble efforts" for handling tail recursion in the compiler frontend? Do you already have an idea of what this would look like?