This is another missing optimization.

We often have parsers that have nested <seq>....</seq>

This is never needed as these can be merged. This improves tracing and debugging by avoiding having these excess things there.

It also simply reduces the number of parser 'actions' a bit, so can't hurt for performance reasons. Every parsed element seems to have at least one excess <seq>...</seq> created around it.