Panic in the intersection function

[wzjsun]

Code to reproduce:：

use geo::{BooleanOps, Polygon, Coord, LineString};

#[test]
fn test() {
        // Reproduction occurs when intersecting Polygon<f32> types, but Polygon<f64> does not reproduce.
	let geo1 = Polygon::<f32>::new(LineString(vec![Coord { x: 0.0, y: 0.0 }, Coord { x: 0.0, y: 200.0 }, Coord { x: 200.0, y: 200.0 }, Coord { x: 200.0, y: 0.0 }, Coord { x: 0.0, y: 0.0 }]), vec![] );
	let geo2 = Polygon::<f32>::new(LineString(vec![Coord { x: -0.17588139, y: 0.0015348792 }, Coord { x: 1.5845897, y: 201.73154 }, Coord { x: 200.1759, y: 199.99846 }, Coord { x: 198.41544, y: -1.7315454 }, Coord { x: -0.17588139, y: 0.0015348792 }]), vec![] );
	let r = geo1.intersection(&geo2);
	println!("r=================={:?}", r);
}

Output:：

---- test stdout ----
thread 'test' panicked at 'segment not found in active-vec-set: 1', C:\Users\chuanyan\.cargo\registry\src\github.com-1ecc6299db9ec823\geo-0.26.0\src\algorithm\sweep\vec_set.rs:22:14 

[RobWalt]

You encountered one of the many issues that are still left open with the implementation of BoolOps in geo. Please refer to #976

Edit: And thanks for the example test! 👍

[RobWalt]

I added this as a test to #1089 and it passes.

[michaelkirk]

I just merged #1234 which replaces our BoolOps implementation with one backed by the i_overlay crate. This should resolve the issue you're seeing. Let us know if it recurs. You can use it now if you use the unreleased geo crate, otherwise we expect it to be part of the upcoming v0.29.0 release.