Iterator invalidation, like pointer invalidation, remains a thing. Iterators and pointers are normally treated as ephemeral, except where guarantees are provided.
It is hard for me to imagine how "the compiler is well exercised and tested" could be perceived to mean the opposite. Explain?
It is hard for me to imagine how "the compiler is well exercised and tested" could be perceived to mean the opposite. Explain?