Katherine

There's also reordering, and I suppose we either refrain from doing that, or we error about it as an unsupported situation.

Hm thank you, I'll try to re-think some of this, too. Maybe we can find a few more situations to cover with tests, although I did think I had covered...

That's fine! Nothing to apologise about!!

Note to myself; I'm just waiting on thinking a bit about some of the AST behaviour here before I go ahead and merge this.

These should be rendered out to roff (and html etc), and all the build system stuff for that is missing. I put quite a bit of work into my own...

@BenBE you're probably right about missing points where we should free, but don't currently (unrelated to the leaks during bad parses). I know I cut some corners for those. We...

@hvdijk thanks for the POC there, that's super helpful. It seems like there are two things going on in your diff; 1. moving the responsibility for where `free()` happens to...

I'm not sure I follow. If we're returning `-> (node :ast_expr)` wouldn't we bind that to a new variable in the .sid file? ``` a = ; // NULL b...

Oh dear :)

> where somehow we would specify what happens when an `:ast_expr` is discarded. Do you think we could add this to sid somehow? There are similar %sections% for implementing copying,...