Page MenuHome

Stabilize boolean's epsilon use, write tests
Confirmed, NormalPublicTO DO


Motivation: resolve bugs in boolean code.


Currently booleans use epsilon comparisons in a non-uniform way,
causing near edge-cases for fall in-between detecting a segment and an end-point intersection.

This would resolve some of the open bug reports we have now.

Estimated Time: 2 weeks

  • 1 week writing tests, make sure existing bug reports are covered by these tests.

    This is very important since currently there aren't any good ways to know if a change to boolean code breaks edge cases.
  • 1 week (max) to go over current boolean code and make all comparisons uniform

    (may be a day or two as well, just needs to be done carefully, possibly re-working intersection code)