Subject: Re: [geometry] rtree Value requirements
From: Barend Gehrels (barend_at_[hidden])
Date: 2012-12-13 16:25:51
On 13-12-2012 18:10, Adam Wulkiewicz wrote:
> I've used static_vector instead of array in nodes for a compile-time
> version of the rtree. From the user's point of view this change means
> that Values are destroyed exactly when remove() is called. For
> example, shared_ptrs will release the memory exactly when one requests
> I'm thinking about other change. For now default ctor is a
> requirement. I'm considering removing this requirement to allow using
> of the rtree for Values only with defined copy ctor and assignment op.
About intersects/disjoint, combinations for point/polygon, point/ring
and point/multi_polygon are now implemented, will commit this tomorrow.
Geometry list run by mateusz at loskot.net