Most of the nesting tree-traversal logic I have on hand assumes snarl ids are unique across vcf sites. This breaks when producing many records per snarl (as could arise with cycles). This PR deactivates it for now (note: this only applies to the new -n option) -- turning it back on will require updating the ids (or tags) to carry more information.
Most of the nesting tree-traversal logic I have on hand assumes snarl ids are unique across vcf sites. This breaks when producing many records per snarl (as could arise with cycles). This PR deactivates it for now (note: this only applies to the new
-noption) -- turning it back on will require updating the ids (or tags) to carry more information.