Exception safety

Exception safety is the state of code working correctly when exceptions are thrown. To aid in ensuring exception safety, C++ standard library developers have devised a set of exception safety levels, contractual guarantees of the behavior of a data structure's operations with regards to exceptions. Library implementers and clients can use these guarantees when reasoning about exception handling correctness. The exception safety levels apply equally to other languages and error-handling mechanisms.

History
As David Abrahams writes, "nobody ever spoke of 'error-safety' before C++ had exceptions." The term appeared as the topic of publications in JTC1/SC22/WG21, the C++ standard committee, as early as 1994. Exception safety for the C++ standard library was first formalized for STLport by Abrahams, establishing the basic safety/strong safety distinction. This was extended to the modern basic/strong/nothrow guarantees in a later proposal.

Background
Exceptions provide a form of non-local control flow, in that an exception may "bubble up" from a called function. This bubbling can cause an exception safety bug by breaking invariants of a mutable data structure, as follows:


 * 1) A step of an operation on a mutable data structure modifies the data and breaks an invariant.
 * 2) An exception is thrown and control "bubbles up", skipping the rest of the operation's code that would restore the invariant
 * 3) The exception is caught and recovered from, or a   block is entered
 * 4) The data structure with broken invariant is used by code that assumes the invariant, resulting in a bug

Code with a bug such as the above can be said to be "exception unsafe".

Classification
The C++ standard library provides several levels of exception safety (in decreasing order of safety):
 * 1) No-throw guarantee, also known as failure transparency: Operations are guaranteed to succeed and satisfy all requirements even in exceptional situations. If an exception occurs, it will be handled internally and not observed by clients.
 * 2) Strong exception safety, also known as commit or rollback semantics: Operations can fail, but failed operations are guaranteed to have no side effects, leaving the original values intact.
 * 3) Basic exception safety: Partial execution of failed operations can result in side effects, but all invariants are preserved. Any stored data will contain valid values which may differ from the original values. Resource leaks (including memory leaks) are commonly ruled out by an invariant stating that all resources are accounted for and managed.
 * 4) No exception safety: No guarantees are made.

Usually, at least basic exception safety is required to write robust code. Higher levels of safety can sometimes be difficult to achieve, and might incur an overhead due to extra copying. A key mechanism for exception safety is a  clause, or similar exception handling syntax, which ensure that certain code is always run when a block is exited, including by exceptions. Several languages have constructs that simplify this, notably using the dispose pattern, named as,  , or  -with-resources.

Example
Consider a smart vector type, such as C++'s or Java's. When an item is added to a vector, the vector must actually add  to the internal list of objects and update a count field that says how many objects are in. It may also need to allocate new memory if the existing capacity isn't sufficient.

Exception safety alternatives:
 * No-throw guarantee: Implemented by ensuring that memory allocation never fails, or by defining the function's behavior on allocation failure (for example, by having the function return a boolean result indicating whether the insertion took place).
 * Strong exception safety: Implemented by doing any necessary allocation first, and then swapping buffers if no errors are encountered (the copy-and-swap idiom). In this case, either the insertion of into  succeeds, or  remains unchanged despite the allocation failure.
 * Basic exception safety: Implemented by ensuring that the count field is guaranteed to reflect the final size of . For example, if an error is encountered, the function might completely deallocate  and reset its count field to zero. On failure, no resources are leaked, but 's old value is not preserved.
 * No exception safety: An insertion failure might lead to corrupted content in, an incorrect value in the count field, or a resource leak.