Subject: Re: [boost] [Review Request] Inclusion of the Boost.Polygon Voronoi Library
From: Simonson, Lucanus J (lucanus.j.simonson_at_[hidden])
Date: 2012-05-23 15:54:50
>As a side note, we would probably need to have two counters: one for points and one for segments.
>Additional point sites (segment endpoints) that are not actually part of the input could have the same index as
>related input segment and its up to the output data structure to decide how to treat them for the inplace implementation.
I think a single index would be simpler on our side and if the user requires different data types for point and segment they can handle that on their end with a simple abstraction on top of the index such as indexing to a boost any. Having two different types of index doesn't enable anything, it simply makes one specific use case more convenient. Common use cases will be only points or only segments in the input, so complicating the interface for the mixed case seems like over design.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk