Daniel James 8229aa6b3c Stop throwing exception in allocator copy/assignment ...

The standard specifies that all of these "shall not exit via an
exception". The containers have been exception safe when these throw,
but the 'noexcept' attribute on 'get_allocator' will terminate if an
exception is thrown in the copy constructor.

The standard doesn't specify a default constructor, so that is allowed
to throw an exception (not just pedantry, this makes sense if an
allocator has shared data that's allocated in the initial constructor).

2017-04-23 11:01:04 +01:00

..

cxx11_allocator.hpp

Reformat with clang-format

2017-02-19 13:05:17 +00:00

exception.hpp

Stop throwing exception in allocator copy/assignment

2017-04-23 11:01:04 +01:00

fwd.hpp

Reformat with clang-format

2017-02-19 13:05:17 +00:00

minimal.hpp

Stricter about rebinding the allocator

2017-02-23 20:14:27 +00:00

test.hpp

Test that construct/destroy aren't used when C++11 isn't available

2017-04-18 10:14:26 +01:00