Exception safety of std::deque operations

Most operations on std::deque provide strong exception safety, meaning if an exception is thrown, the deque remains in a valid state and no resources are leaked.

Operations that provide strong exception safety include:

• push_front(), push_back(), emplace_front(), emplace_back()
• pop_front(), pop_back()
• insert(), emplace(), erase()
• clear(), swap()

However, there are a few operations that only provide basic exception safety, meaning if an exception is thrown, the deque is left in a valid but unspecified state.

Operations with basic exception safety:

• deque(size_type n, const T& value) and deque(InputIt first, InputIt last) constructors
• operator=
• assign(), resize()

For these operations, if an exception is thrown during the operation (for example, when copying elements), some elements might be constructed, copied, or destroyed, but the deque will still be in a valid state.

Here's an example of how push_back() maintains strong exception safety:

1template <typename T>
2void Deque<T>::push_back(const T& value) {
3  if (backIndex == blockSize) {
4    allocateNewBlock();  
5    backIndex = 0;
6  }
7  try {
8    new (&blocks_[backBlock_][backIndex])
9      T(value);  
10  } catch (...) {
11    if (backIndex == 0) {
12      deallocateLastBlock();  
13    }
14    throw;
15  }
16  ++backIndex;
17}

If the constructor of T throws an exception, the deque's state is rolled back by deallocating the block if it was newly allocated.