Title
std::allocator needs to be a concept-constrained template
Status
nad concepts
Section
[default.allocator]
Submitter
Alisdair Meredith

Created on 2009-03-11.00:00:00 last changed 172 months ago

Messages

Date: 2010-10-21.18:28:33

[ Summit: ]

Agree as stated. A future paper will address additional related issues.

Date: 2012-10-21.13:19:07

Addresses UK 213 [CD1]

std::allocator should be constrained to simplify its use on constrained contexts. This library component models allocation from free store via the new operator so choose constraints to match. The Allocator concept allows for a wider variety of allocators that users may choose to supply if their allocation model does not require operator new, without impacting the requirements of this template.

Suggested direction:

The primary allocator template should be constrained to require ObjectType<T> and FreeStoreAllocatable<T>. Further operations to be constrained as required.

History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg373
2009-03-11 00:00:00admincreate