Set parent pointers as nodes are ready in parser, rather than all at once as parse is complete#1279

Merged

weswigham merged 12 commits intomicrosoft:mainfrom

weswigham:set-parents-upfront

Jun 26, 2025

Commits on Jun 24, 2025

Set parent pointers as nodes are ready in parser, rather than all at once as parse is complete
weswigham
committed
Test parent invariant, violations everywhere
weswigham
committed
Use inlinable closures instead of methods
weswigham
committed
You know, forEachChild is basically a go iterator already
weswigham
committed
Why is the performant thing not the idiomatic thing? This looks horrid.
weswigham
committed
bugfix, still assertion failures to track down and except
weswigham
committed
Catalogue the remainder of the current exceptions to the parent pointer invariant maufactured by the js reparser
weswigham
committed
The slight differences in which parent are selected for jsdoc reparsing cause these diffs - they seem like improvements, at least
weswigham
committed

Commits on Jun 25, 2025

Commits on Jun 26, 2025

Merge branch 'main' into set-parents-upfront
weswigham
committed