New
Bugfix: spurious 0 value no longer returned
A recently implemented opcode used for efficiency in {N,M} type
patterns, was returning the index 0 for a null match, instead of
the index it was testing. This would result in an invalid slice
when creating the match object. No longer.