geometry
geometry copied to clipboard
boostorg
Set operation strategies are undocumented
In documentation, there are links for set operations with the use of strategies e.g. difference (with strategy), see below for more. However, the description on the use of the strategy seems loose, e.g. the example is identical to the original (without strategy) function.
Is this on purpose? If not this could be fixed.
https://www.boost.org/doc/libs/1_75_0/libs/geometry/doc/html/geometry/reference/algorithms/difference/difference_4_with_strategy.html https://www.boost.org/doc/libs/1_75_0/libs/geometry/doc/html/geometry/reference/algorithms/union_/union__4_with_strategy.html https://www.boost.org/doc/libs/1_75_0/libs/geometry/doc/html/geometry/reference/algorithms/intersection/intersection_4_with_strategy.html https://www.boost.org/doc/libs/1_75_0/libs/geometry/doc/html/geometry/reference/algorithms/sym_difference/sym_difference_4_with_strategy.html
@pcmourya No need to ask for permission. There is no reservation of issues or tasks in use. First PR submitted, first PR reviewed and first PR has chance to be merged first.
I could not find any pre defined strategies in the official documentation for set operations mentioned above. So do we have to define a custom strategy and add it to the example codes? It would be helpful if @vissarion could clarify on this.
is this on purpose? If not this could be fixed.
I think strategies for these operations are not yet defined, that's why the same example is used on both functions. But using the same example on both functions can be misleading, I guess it needs to be removed from the with strategies part, till the strategies are defined.
I think it is OK to stay as is until the strategies are documented and properly linked as available strategies in the algorithm documentation. Also note that recently set operations were refactored see https://github.com/boostorg/geometry/pull/768