Boolean difference causes panic: `segment not found` about geo HOT 6 OPEN

Does it work with f64? I suspect there's a reason why other libraries use double precision.

from geo.

Yes this test passes with f64.

from geo.

The issue in #913 is equally possible for any floating point representation, but less probable as precision increases.

I'm not sure if this issue is the same underlying cause as #913.

from geo.

Right, it can still happen, but it does make sense to use higher than input precision for computation. Not an elegant solution, but worth considering.

from geo.

Understood, we'll change our codebase to use f64.

For some context, we're currently using f32 only because we're generating vertex buffer data that gets fed into WebGL, and out of laziness we're avoiding a f64 => f32 conversion step.

from geo.

Update: unfortunately we can still easily reproduce a similar panic after changing our codebase to use 64-bit precision.

from geo.