Subject: [geometry] rtree Value requirements
From: Adam Wulkiewicz (adam.wulkiewicz_at_[hidden])
Date: 2012-12-13 12:10:30
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 it.
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.
Geometry list run by mateusz at loskot.net