added a couple more test cases
added code that removes duplicate turns;
relate(L,L) handled G1 last range point boundary in the exterior of G2
relate(L,L) some tests added - tests for linear rings not passed, added note about the error
relate(L,L) added exit_operation to exit_watcher
[geometry] Fixed results for distance of integer point types point-segment
or point-linestring
relate(L,L) the algorithm analysing one turn enclosed within turn_analyser
relate(L,L) fixed some compilation errors for MultiLinestrings, some parts of the code temporarily commented out, added failing test - currently used algorithm is analysing only those Linestrings which are intersecting the other geometry, other ones are NOT taken into account
Merge branch 'feature/relate' of https://github.com/boostorg/geometry into feature/setops
Merge branch 'develop' of https://github.com/boostorg/geometry into feature/setops
relate(L,L) added asserts to boundary_checker
relate() boundary_checker moved to separate file
added point_in_point agnostic strategy and point_in_geometry() for Point and MultiPoint
relate() added has_disjoint_sub_geometries check - not working for all special cases, should be replaced with e.g. for_each_disjoint_sub_geometry
relate(L,L) - restored asserts in boundary_checker, added proper calculation of seg_ids for the first and last point of a range
relate(L,L) has_disjoint_sub_geometries simple check replaced by for_each_disjoint_linestring_if taking predicate checking linestrings
relate(L,L) disjoin linestrings contained in multilinestring properly handled. In the case of disjoint linestrings almost all special cases are handled non-simple linear rings, 1-point linestrings. Linestrings containing >1 equal points are for now treated as normal linear rings, this should probably be changed.
relate(L,L) handled some cases with 1-point linestrings involved (if 1-PtLS is disjoint or there are other Ls in the other MLs)
[geometry] Fix for integer-distance-point-to-polygon,
submitted by Menelaos Karavelas
relate(L,L) handled the rest of cases with 1-point linestrings involved, added interrupt member to relate result - it may be used to break the calculation