| Issue |
Status |
Section |
Title |
Proposed Resolution |
Duplicates |
| 31 |
WP |
14.9.1.1 [concept.fct] |
Which specifiers are legal for associated functions? |
Yes |
|
| 26 |
WP |
17 [library] |
Transition of Clause 17, Library introduction |
Yes |
|
| 5 |
WP |
20.1 [utility.concepts] |
Inconsistent naming between concepts and type traits |
Yes |
|
| 10 |
WP |
20.1 [utility.concepts] |
Remarks should be notes |
Yes |
|
| 40 |
WP |
20.1 [utility.concepts] |
HasXXX concepts should not default second parameter when there is an XXXable concept |
Yes |
|
| 27 |
WP |
20.1.1 [concept.support] |
Missing core concept for polymorphic types |
Yes |
|
| 28 |
WP |
20.1.1 [concept.support] |
Abstract classes should not be VariableTypes |
Yes |
|
| 1 |
WP |
20.1.2 [concept.comparison] |
Naming and symmetry in EqualityComparable |
Yes |
|
| 2 |
WP |
20.1.3 [concept.destruct] |
Requires clause for Destructible is unclear |
Yes |
|
| 3 |
WP |
20.1.4 [concept.construct] |
Naming of Constructible/DefaultConstructible concepts |
Yes |
|
| 32 |
WP |
20.1.4 [concept.construct] |
Missing definition of TriviallyDefaultConstructible |
Yes |
|
| 4 |
WP |
20.1.5 [concept.copymove] |
MoveConstructible should refine Constructible |
Yes |
|
| 6 |
WP |
20.1.5 [concept.copymove] |
MoveAssignable assignment operator is incorrect |
Yes |
|
| 35 |
WP |
20.1.5 [concept.copymove] |
Swappable should be usable with proxy iterator references |
Yes |
|
| 9 |
WP |
20.1.6 [concept.memory] |
Memory-allocation concepts are too fine-grained |
Yes |
|
| 12 |
WP |
20.1.10 [concept.operator] |
Update operator concepts based on "Option #2" change in language specification |
Yes |
|
| 13 |
WP |
20.1.10 [concept.operator] |
Naming consistency in [concept.operator] |
Yes |
|
| 14 |
WP |
20.1.10 [concept.operator] |
Addressable and const types |
Yes |
|
| 15 |
WP |
20.1.10 [concept.operator] |
Can Callable's function object be an rvalue? |
Yes |
|
| 36 |
WP |
20.1.10 [concept.operator] |
HasCopyAssign should be named HasAssign |
Yes |
|
| 33 |
WP |
20.1.11 [concept.arithmetic] |
ArithmeticLike should have construction from an unsigned integral type |
Yes |
|
| 47 |
WP |
20.1.11 [concept.arithmetic] |
ArithmeticLike conversions from integral, floating-point types should be explicit |
Yes |
|
| 17 |
WP |
20.1.13 [concept.allocator] |
Errors in Allocator concept |
Yes |
|
| 34 |
WP |
23 [containers] |
Copy/move requirements on container members |
Yes |
|
| 38 |
WP |
23 [containers] |
Container move constructor/assignment operators don't account for scoped allocators |
Yes |
|
| 48 |
WP |
23.1.4 [container.concepts] |
Missing iterator to const_iterator conversion |
Yes |
|
| 18 |
WP |
24.1 [iterator.concepts] |
Consistent naming for concepts headers |
Yes |
|
| 19 |
WP |
24.1 [iterator.concepts] |
IteratorBase is an implementation detail |
Yes |
|
| 22 |
WP |
24.1.1 [input.iterators] |
Oddly-placed and missing InputIterator requirements |
Yes |
|
| 23 |
WP |
24.1.2 [output.iterators] |
Output iterators without value types |
Yes |
|
| 25 |
WP |
24.1.3 [forward.iterators] |
Lost normative semantics of ForwardIterator |
Yes |
|
| 29 |
WP |
25 [algorithms] |
Concepts on mutating algorithms are confusing |
Yes |
|
| 30 |
WP |
25 [algorithms] |
Should Predicates be on Iter::value_type or Iter::reference? |
Yes |
|
| 39 |
WP |
25 [algorithms] |
Some uses of the MutableXXXIterator concepts are unnecessary |
Yes |
|
| 43 |
WP |
25 [algorithms] |
Using Swappable for all swapping |
Yes |
|
| 45 |
WP |
25.2.2 [alg.move] |
move and move_backward rely too heavily on the iterator's value_type |
Yes |
|
| 44 |
WP |
25.2.9 [alg.unique] |
unique_copy requirements don't account for move semantics |
Yes |
|