Michael Kirk

I'm not very familiar with the bool ops implementation yet, but I did want to try to help solve this issue. To start with, I reproduced a similar error with...

I thought I left a response on this long ago, sorry for letting the thread drop. Unfortunately I didn't take very good notes either, but as I recall the root...

> IIRC, this panic is happening when we have two very close intersections, such that the amount of error in the f64 representation of the intersection is enough to break...

This seems useful, and indeed the LineInterpolatePoint/LineLocatePoint seems like good inspiration, since they're in the same spirit. As you say, they both take input parameters as a "ratio" of the...

This third one actually seems reasonable to me: ``` #[test] fn x_out_of_range() { // x is out of long rannge but will compute fine let x = point!( x: -361_f64...

That seems like a useful addition to me.

A `MultiPolygon` is implemented as a `Vec` of `Polygons`, so if you need an object of Polygon, you can take the `Polygon` from the inner Vec. ``` use geo::{MultiPolygon, Polygon,...

> it might be possible to do something similar still. Since Deref will be applied recursively, doesn't this leave us at the same place as you were trying to avoid,...

Thanks for moving us into the ✨Future✨ @martinfrances107! > PS: we could probably drop support for that old rstar, and I'm not sure what we're using the previous version of...

I believe this is a dupe of https://github.com/georust/geo/issues/913 That issue is still open - but let's try to focus any future discussion on this bug there. Note there may be...