Unordered Waters

Practising this hard C++ language-knowledge question

This is a hard code-reading question that tests your depth of understanding C++ semantics, particularly around container behaviour, iterator validity, and standard library edge cases. Firms ask these questions to distinguish candidates who have read and reasoned about the standard carefully from those who rely on intuition alone.

To solve problems like this, you need to trace through the code mentally, paying close attention to the state of each object after each operation, the behaviour of iterators under mutation, and any implicit conversions or type deductions that occur. The question rewards precision: a small detail you might overlook in production code becomes the crux of the answer here.

• Container invariants and iterator stability
• Unordered container semantics and rehashing
• Order of evaluation and side effects
• Standard library guarantees and undefined behaviour