add `node.getAllAncestorsAtRange` method

Do you want to request a feature or report a bug?

Feature.

What’s the current behavior?

Right now you have to manually iterate the blocks and look up each of their ancestors, and then make sure you convert it to a set to remove duplicates.

What’s the expected behavior?

It would be nice to have a getAllAncestorsAtRange method that returned all of the ancestors in the range exactly once, so you can more easily find wrapping parents of certain types.

[Dundercover]

Sounds good @ianstormtaylor, I’ll jump on this next.

The getContainedXAtRange methods do definitely feel like they could be useful for a lot of use cases. I do think though that we should create a separate issue for those to not spread this issue too wide.

[Dundercover]

Sounds good @ianstormtaylor, lets go with Root/Leaf then.

For the All, I think it works either way (I think I’m leaning more towards without the All tbh) but just so we could deprecate the existing methods (getBlocksAtRange, etc). If we prefer without the All, we could remove it later with another deprecation period.

I could also skip any changes to the current API methods and just add the getNodesAtRange for now?