Hi,

this looks almost what I need for my project. I skimmed through the source. Sadly two requirements do not seem fulfilled for my use case.

1. move a point p1 to another point p2: tree.update(p1: Point,p2: Point) without rebuilding the whole octree (and of course also be able to remove it later).
2. equip each Point with an id number in order to be later able to identify it in the results: for instance have a type Point like this: pub type Point = (f64, f64, f64, u64).

then you could write:

		pub type Point = (f64, f64, f64, u64);
		let mut points: Vec<Point> = Vec::new();
		points.push((5.0,2.0,8.0,101));//testdata
		points.push((10.0,3.0,2.0,1,205));//testdata
		points.push((10.0,13.0,12.0,48));//testdata
		points.push((10.0,3.0,2.0,3,10000));//testdata

		let mut tree = Octree::new(&points);
		tree.bucket_size = 8*8;
		tree.build();

		let x:Point = [0.0,0.0,0.0];
		let neighbors=tree.search(x,15.0);
		println!("{:?}",neighbors);

Output [(101, 9.643650760992955), (205, 10.63014581273465), (10000, 10.63014581273465)]

Is this something your library would support in future?

Thank you for the crate. I just have a simple mutable reference problem.

As we can see Octree has a immutable reference to the points. Now say we have a simulation, where points will change their position with time. If the octree is active, then we will have a mutable reference problem, since octree has a mutable reference to the points and we are trying to update them.

How to deal with such a situation? Do you have any crate where you use this crate and solve did some simulation?