splice() on std::list and iterator invalidation

Question

The 3-argument form of list::splice() moves a single element from one list to the other. SGI\'s documentation explicitly states that all iterators, includi

Answer 1

I have an array of lists (equivalence classes of elements), and I'm using splice to move elements between the lists. I have an additional array of iterators which gives me direct access to any element in any of the lists and to move it to another list. None of the lists is searched and modified at the same time. I could reinitialize the element iterator after splice, but it's kinda ugly.. I guess I'll do that for the time being.

Answer 2

The problem is that if the iterator still points to the element that was moved, then the "end" iterator previously associated with the "moved" iterator has changed. Unless you write some complex loop, this is actually a bad thing to do -- especially since it will be more difficult for other developers to understand.

A better way in my opinion is to use the iterators pointing to the elements prior and after the moved iterator.

Answer 3

Ok, this seems to be a defect in the standard, according to this and this link. It seems that "sticking the head in the sand" is a good strategy, since it will be fixed in new library versions.