boost_unordered

T

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

doc

Intro to compliance section

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

examples

Remove unary/binary_function from examples/documentation

2016-11-06 10:19:17 +00:00

include/boost

Remove a TODO

2017-04-23 10:51:17 +01:00