> Fixing that requires the intrusively merged linked list to go from singly- to > doubly- linked and @Araq does not like to charge "non-delete workload" cases > for things only needed by mixed workloads. (In this case the charge is space > for the 2nd link.)
That's true but I think a more radical change of the implementation can give us O(1) deletions without the memory overhead. Haven't really thought about it though.
