Shannon Stewman

> A quite decisive argument against a pool allocator is that it interferes with normal memory checker instrumentation and may hide buffer overread, double-free and uninitialized memory read/write issues. A...

> I agree! Ideally this would be purely part of `parser.act`, where somehow we would specify what happens when an `:ast_expr` is discarded. Unfortunately sid does not support this, so...

@katef sounds good. I do like the idea of a `%destructors%` section, but I also have no desire to learn enough of the insides of `sid` to design or implement...

Here's where the spec states that this is okay: http://www.pcre.org/current/doc/html/pcre2pattern.html#SEC17 > An opening curly bracket that appears in a position where a quantifier is not allowed, or one that does...

Possibly. It's interesting to consider forcing sid into a backtracking parser.

> @dgryski I think we should move this logic up a level, to the vm, and introduce an opcode for this, or replace the existing "match a character" with "match...