You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for alternative Hierarchy representations
The current Hierarchy component implementation contains a parent pointer on each hierarchy::NodeData. This provides O(1) access to a node's parent, but requires accessing every children during a transplantation operation where we swap a parent for another node.
An alternative representation may only include the parent pointer on the first/last sibling, to invert the mentioned constant and linear costs.
A middle ground compromise could use a skip list, where most operations cost O(log n).
We could also explore replacing the intrusive linked lists by children node blocks on the parent. This would consume more memory but may end up being more efficient.
The text was updated successfully, but these errors were encountered:
This is a tracking issue for alternative Hierarchy representations
The current
Hierarchy
component implementation contains a parent pointer on eachhierarchy::NodeData
. This provides O(1) access to a node's parent, but requires accessing every children during a transplantation operation where we swap a parent for another node.O(log n)
.The text was updated successfully, but these errors were encountered: