Issue with "remove" method about jvptree HOT 3 OPEN

I think I found the bug. In the anneal method, where one of the children is empty, these lines

            if (closerSize == 0 || fartherSize == 0) {
                // One of the child nodes has become empty, and needs to be pruned.
                this.points = new ArrayList<>(closerSize + fartherSize);
                this.addAllPointsToCollection(this.points);

mean that the test for this.points == null in addAllPointsToCollection fails. Something like this works

            if (closerSize == 0 || fartherSize == 0) {
                // One of the child nodes has become empty, and needs to be pruned.
                ArrayList<E> children = new ArrayList<>(closerSize + fartherSize);
                this.addAllPointsToCollection(children);
                this.points = children;

from jvptree.

I think you're right and will follow up shortly.

It's funny—I was actually thinking the other day that the "anneal" process is so complicated and inefficient that it really ought to change or go away. A challenge for another time, though.

from jvptree.

Thanks!

"anneal" would be a lot simpler if you didn't need to worry about points being removed from the tree.

Just to make things a bit more complicated ... I was thinking a bit more about the pruning logic. It's possible that a new vantage point could be chosen in that step? When you construct the tree every vantage point is one of the points inserted into the tree. That won't be the case when you start removing things?

from jvptree.