TreeNode depth is likely sometimes incorrect
Open
audit
P3
- Dominant language
- Dart
- Stars
- 1.7k
- Forks
- 404
- Avg merge
- 6d 17h
- Merged PRs (30d)
- 18
Description
TreeNode.depth assumes that TreeNodes are not modified after the first time depth is accessed but it likely code violates this assumption.
We should probably instead switch to a scheme where TreeNode depth values are invalidated when the tree structure bellow them changes although this needs to be done with care to avoid excessive computations of depth.
Contributor guide
Assessment
This issue has not been assessed yet.