Hi Matthias,
I would agree with you that for most applications the order should not matter. However, a sequential "vector style" writer (e.g. typical e-beam writer which skips empty regions) has to in the end choose the order of the shape…
Thanks for the info Matthias! I'm sure manipulating the binary directly would be the fastest way to take care of this issue.
As an alternative, I'm think that one could overload db::Shapes::begin so that it accepts a comparison function and iterate…