...works fine with one container but would invalidate iterators on another, or... The list goes...

...know insertAtRandom won't and *can't* invalidate your iterators/ranges, and you don't...

...a vector container, expanding the container would invalidate ranges. Instead of allowing ranges to become...

...thinking that events could be used to
invalidate
ranges if the container changed, i.e...

...e. "softXxx") for primitives that don't invalidate iterators. That moves the documentation into the...

...You can also force the container to invalidate itself once the first wrap occurs.  This...

...modifications in general aren't and might invalidate all pointers to the structure.
Exceptions to...

...using documentation to indicate insertion will not invalidate ranges.  Perhaps I am wrong.

I was...

...an element from an array doesn't invalidate the underlying range, since the memory is...

...better to say "they are assumed to invalidate linked ranges". I know it's the...