Sonic78
Reputation: 808
Why is std::allocator::deallocate not noexcept?
The C++ specification (ISO/IEC 14882:2011 + ISO/IEC 14882:2014) defines in Table 28 — Allocator requirements for deallocate:
All n T objects in the area pointed to by p shall be destroyed prior to this call. n shall match the value passed to allocate to obtain this memory. Does not throw exceptions.
But why is deallocate still not noexcept?
Upvotes: 5
Views: 545
Answers (1)
T.C.
Reputation: 137425
It's narrow contract (causing undefined behavior if you pass it a pointer not returned by allocate, for instance), so per the standard library's usual policy it's not marked noexcept.
Upvotes: 5
Related Questions
- Difference between "destroy" "destructor" "deallocate" in std::allocator?
- Why deallocation function is not called when object constructor throw in a new expression?
- why does std::allocator::deallocate require a size?
- why does the standard let me free-store allocate classes without destructors?
- std::allocator deallocate part of memory
- Does deallocation imply destruction?
- Why is a pointer not permitted to be null when calling the deallocate method of the allocator class?
- C++ allocator<X>::deallocate(NULL,1) allowed?
- Why does std::allocator<>::deallocate() have a size_type parameter which is not used?
- What is the purpose of the second parameter to std::allocator<T>::deallocate?