7313913127
The 2 existing usages of `remove_node` always operated on a child and its parent: One iterates over all of its children and removes each one, and the other explicitly grabs the parent of a given node. As a simplification, `remove_node` operates only on a child node, without the need for the parent node in addition; it grabs the parent from the child by itself. As such, it's non-failable. |
||
---|---|---|
.. | ||
assets | ||
macros | ||
src | ||
Cargo.toml |