Re: noverlay branch

[Stefan Monnier]

> to allow C++.  With std::multimap/std::multiset, we would have a
> ready-made complete solution for the tree, tested by a gazillion of
> users.  Just dreaming :-))

I'm not familiar with C++ libs: does this `multiset` lib offer something
similar to the lazy update of buffer positions that Andreas's code uses
(via the `offset` field together with the `interval_tree_inherit_offset`
function)?

>> I think in the context of this overlay work the performance difference
>> is not very significant, since the code is doing a lot of other stuff
>> while traversing the tree.
> I agree.  I think NULL could be better in multi-threaded cases, as
> Stefan alluded to.

The current code should be multi-thread safe (except for the global
iterator, of course), despite its use of a global sentinel node: there's
no need to synchronize anything when reading a read-only field or when
writing a write-only field.


        Stefan