Fix #29: re-build the KdTree when doing consecutive insert_bulk operations

[timbeurskens]

This PR should fix issue #29

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.57%. Comparing base (56d4487) to head (0aad6fe).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #30      +/-   ##
==========================================
+ Coverage   72.52%   73.57%   +1.04%     
==========================================
  Files          10       10              
  Lines        2038     2100      +62     
==========================================
+ Hits         1478     1545      +67     
+ Misses        560      555       -5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[habedi]

Hi, can the test be more strict? Right now, it only check the tree includes the expected number of points. It doesn't check if the inserted points actually exists in the tree, for example points "L" to "V" should be in the tree.

For example:

for point in points_first.iter().chain(points_second.iter()) {
        assert!(
            tree.contains(point),
            "Expected tree to contain point after consecutive insert_bulk calls: {:?}",
            point
        );

[timbeurskens]

Thanks for the suggestion. I've updated the test accordingly.

[habedi]

Thanks.