tqa-0001 TaxonomyElem creation too expensive for SaxonElem backing element

[dvreeze]

Recursive TaxonomyElem creation looks at the parent element to distinguish between global and local element declarations, for example. The way the parent element is determined is not through a call to method parentOption, but through a call to method reverseAncestryOrSelfENames instead. The latter is optimal if the backing element is a native yaidom indexed element, but quite inefficient (and generating lots of garbage) for Saxon wrapper elements. This should be fixed.

The fix could be twofold:

• During TaxonomyElem creation, reduce the number of parent element/EName calls, by passing the parent around
• Make parent element/EName querying itself very efficient, with custom implementations for well-known backing elements

About the second point: we could have an (internal) element query API extension API, one "instanceof" pattern match for well-known backing element implementations, and then type-safe implementations of that query API extension for those element implementations. One method in that extension query API could be "hasParentWithName(ename)", and it would have quite different implementations for Saxon wrappers and native yaidom indexed elements.

This could all be done in TQA (no need to change yaidom), without any breaking changes.

[dvreeze]

This was fixed in version 0.9.0, by the first proposed solution of passing the parent around in private factory methods.

[dvreeze]

See above.