| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 3105 |
New |
15 [library] |
T1 is convertible to T2 |
No |
3 |
|
| 2949 |
New |
15 [library] |
Unclear complexity requirements: space vs. time |
No |
4 |
|
| 1195 |
C++11 |
15 [library] |
"Diagnostic required" wording is insufficient to prevent UB |
Yes |
|
|
| 1349 |
C++11 |
15 [library] |
swap should not throw |
Yes |
|
|
| 182 |
CD1 |
15 [library] |
Ambiguous references to size_t |
Yes |
|
|
| 230 |
CD1 |
15 [library] |
Assignable specified without also specifying CopyConstructible |
Yes |
|
|
| 336 |
CD1 |
15 [library] |
Clause 17 lack of references to deprecated headers |
Yes |
|
|
| 2925 |
Resolved |
15 [library] |
Template argument deduction is not used in the standard library |
Yes |
|
|
| 343 |
Resolved |
15 [library] |
Unspecified library header dependencies |
Yes |
|
|
| 625 |
Resolved |
15 [library] |
Mixed up Effects and Returns clauses |
Yes |
|
895 |
| 1151 |
Resolved |
15 [library] |
Behavior of the library in the presence of threads is incompletely specified |
Yes |
|
|
| 1344 |
Resolved |
15 [library] |
Replace throw() with noexcept |
Yes |
|
1351 |
| 1345 |
Resolved |
15 [library] |
Library classes should have noexcept move operations |
Yes |
|
|
| 1346 |
Resolved |
15 [library] |
Apply noexcept where library specification does not permit exceptions |
Yes |
|
1352 |
| 1347 |
Resolved |
15 [library] |
Apply noexcept judiciously throughout the library |
Yes |
|
|
| 1353 |
Resolved |
15 [library] |
Clarify the state of a moved-from object |
Yes |
|
|
| 972 |
NAD Editorial |
15 [library] |
The term "Assignable" undefined but still in use |
Yes |
|
|
| 1232 |
NAD Editorial |
15 [library] |
Still swap's with rvalue-references |
Yes |
|
|
| 877 |
NAD |
15 [library] |
to throw() or to Throw: Nothing. |
Yes |
|
|
| 2898 |
NAD |
15 [library] |
Prefer not to use member typedefs as constructor parameters |
Yes |
|
|
| 2865 |
NAD |
15 [library] |
Resolve all open Library issues for C++17 |
Yes |
|
|
| 385 |
NAD |
15 [library] |
Does call by value imply the CopyConstructible requirement? |
Yes |
|
|
| 941 |
NAD |
15 [library] |
Ref-qualifiers for assignment operators |
Yes |
|
|
| 996 |
NAD |
15 [library] |
Move operation not well specified |
Yes |
|
|
| 1099 |
NAD |
15 [library] |
Various issues |
Yes |
|
|
| 1153 |
NAD |
15 [library] |
Standard library needs review for constructors to be
explicit to avoid treatment as initializer-list constructor |
Yes |
|
|
| 1173 |
NAD |
15 [library] |
"Equivalence" wishy-washiness |
Yes |
3 |
|
| 1236 |
NAD |
15 [library] |
reserved identifiers in programs not using the library |
Yes |
|
|
| 1331 |
NAD |
15 [library] |
incorporate move special member functions into library |
Yes |
|
|
| 1348 |
NAD |
15 [library] |
Exception safety of unspecified types |
Yes |
|
|
| 1350 |
Dup |
15 [library] |
Implicit contructors accidentally made some library types move-only |
Yes |
|
1421 |
| 1351 |
Dup |
15 [library] |
Replace dynamic exception specifications with noexcept |
Yes |
|
1344 |
| 1352 |
Dup |
15 [library] |
Apply noexcept where library specification says "Throws: Nothing" |
Yes |
|
1346 |
| 989 |
NAD Concepts |
15 [library] |
late_check and library |
Yes |
|
|
| 1001 |
NAD Concepts |
15 [library] |
Pointers, concepts and headers |
Yes |
|
|
| 1096 |
NAD Concepts |
15 [library] |
unconstrained rvalue ref parameters |
Yes |
|
|
| 2872 |
C++17 |
15.3 [definitions] |
Add definition for direct-non-list-initialization |
Yes |
|
|
| 1354 |
C++11 |
15.3.7 [defns.deadlock] |
The definition of deadlock excludes cases involving a single thread |
Yes |
|
|
| 2392 |
New |
15.3.17 [defns.ntcts] |
"character type" is used but not defined |
No |
3 |
|
| 2136 |
Open |
15.4.1 [structure] |
Postconditions vs. exceptions |
No |
3 |
|
| 424 |
NAD Editorial |
15.4.1.2 [structure.summary] |
normative notes |
Yes |
|
|
| 995 |
NAD |
15.4.1.3 [structure.requirements] |
Operational Semantics Unclear |
Yes |
|
|
| 3168 |
New |
15.4.1.4 [structure.specifications] |
Expects: element should be specified in one place |
Yes |
2 |
|
| 2292 |
New |
15.4.1.4 [structure.specifications] |
Find a better phrasing for "shall not participate in overload resolution" |
No |
3 |
|
| 2679 |
C++17 |
15.4.1.4 [structure.specifications] |
Inconsistent Use of Effects and Equivalent To |
Yes |
3 |
|
| 2710 |
C++17 |
15.4.1.4 [structure.specifications] |
"Effects: Equivalent to ..." doesn't count "Synchronization:" as determined semantics |
Yes |
0 |
|
| 997 |
C++11 |
15.4.1.4 [structure.specifications] |
"Effects: Equivalent to" is underspecified |
Yes |
|
|
| 222 |
TC1 |
15.4.1.4 [structure.specifications] |
Are throw clauses necessary if a throw is already implied by the effects clause? |
Yes |
|
|
| 626 |
NAD Editorial |
15.4.1.4 [structure.specifications] |
new Remark clauses not documented |
Yes |
|
|
| 1179 |
NAD Editorial |
15.4.1.4 [structure.specifications] |
Probably editorial in [structure.specifications] |
Yes |
|
|
| 492 |
NAD |
15.4.1.4 [structure.specifications] |
Invalid iterator arithmetic expressions |
Yes |
|
|
| 663 |
NAD |
15.4.1.4 [structure.specifications] |
Complexity Requirements |
Yes |
|
|
| 895 |
Dup |
15.4.1.4 [structure.specifications] |
"Requires:" on std::string::at et al |
Yes |
|
625 |
| 1156 |
NAD |
15.4.2.1.3 [enumerated.types] |
Constraints on bitmask and enumeration types to be tightened |
Yes |
|
|
| 3092 |
Open |
15.4.2.1.4 [bitmask.types] |
Unclear semantics of enum class bitmask types |
Yes |
2 |
|
| 262 |
CD1 |
15.4.2.1.4 [bitmask.types] |
Bitmask operator ~ specified incorrectly |
Yes |
|
|
| 1357 |
Resolved |
15.4.2.1.4 [bitmask.types] |
Library bitmask types to not satisfy the bimask type requirements |
Yes |
|
|
| 2692 |
NAD |
15.4.2.1.4 [bitmask.types] |
Overspecification of lvalueness of bitmask elements |
Yes |
3 |
|
| 1060 |
NAD Editorial |
15.4.2.1.5.1 [byte.strings] |
Embedded nulls in NTBS |
Yes |
|
|
| 2818 |
New |
15.5.1.1 [contents] |
"::std::" everywhere rule needs tweaking |
No |
2 |
|
| 1065 |
C++11 |
15.5.1.1 [contents] |
Allow inline namespaces within namespace std for implementations |
Yes |
|
|
| 229 |
CD1 |
15.5.1.1 [contents] |
Unqualified references of other library entities |
Yes |
|
|
| 992 |
NAD |
15.5.1.1 [contents] |
Allow implementations to implement C library in the global namespace |
Yes |
|
|
| 2380 |
C++17 |
15.5.1.2 [headers] |
May <cstdlib> provide long ::abs(long) and long long ::abs(long long)? |
Yes |
2 |
|
| 310 |
CD1 |
15.5.1.2 [headers] |
Is errno a macro? |
Yes |
|
|
| 456 |
CD1 |
15.5.1.2 [headers] |
Traditional C header files are overspecified |
Yes |
|
|
| 465 |
CD1 |
15.5.1.2 [headers] |
Contents of <ciso646> |
Yes |
|
|
| 1002 |
NAD |
15.5.1.2 [headers] |
Provide bulk include headers |
Yes |
|
|
| 3148 |
WP |
15.5.1.3 [compliance] |
<concepts> should be freestanding |
Yes |
0 |
|
| 1264 |
C++11 |
15.5.1.3 [compliance] |
quick_exit support for freestanding implementations |
Yes |
|
|
| 1360 |
C++11 |
15.5.1.3 [compliance] |
Add <atomic> to free-standing implementations |
Yes |
|
|
| 833 |
NAD |
15.5.1.3 [compliance] |
Freestanding implementations header list needs review for C++0x |
Yes |
|
|
| 1003 |
NAD |
15.5.1.3 [compliance] |
Require more useful headers for freestanding implementations |
Yes |
|
|
| 1358 |
NAD |
15.5.1.3 [compliance] |
Add <chrono> and <ratio> to
freestanding implementations |
Yes |
|
|
| 1359 |
NAD |
15.5.1.3 [compliance] |
Add <tuple> and <utility> to freestanding implementations |
Yes |
|
|
| 1361 |
NAD |
15.5.2 [using] |
Does use of std::size_t in a header imply that typedef name is available to users? |
Yes |
|
|
| 2428 |
C++17 |
15.5.2.2 [using.headers] |
"External declaration" used without being defined |
Yes |
0 |
|
| 2225 |
C++14 |
15.5.2.2 [using.headers] |
Unrealistic header inclusion checks required |
Yes |
|
|
| 657 |
NAD |
15.5.2.2 [using.headers] |
unclear requirement about header inclusion |
Yes |
|
|
| 1 |
TC1 |
15.5.2.3 [using.linkage] |
C library linkage editing oversight |
Yes |
|
|
| 2281 |
NAD Editorial |
15.5.2.3 [using.linkage] |
C99 cross-reference typo in [using.linkage] |
Yes |
|
|
| 2146 |
Open |
15.5.3.1 [utility.arg.requirements] |
Are reference types Copy/Move-Constructible/Assignable or Destructible? |
No |
2 |
|
| 2170 |
C++17 |
15.5.3.1 [utility.arg.requirements] |
Aggregates cannot be DefaultConstructible |
Yes |
2 |
|
| 724 |
C++11 |
15.5.3.1 [utility.arg.requirements] |
DefaultConstructible is not defined |
Yes |
|
|
| 753 |
C++11 |
15.5.3.1 [utility.arg.requirements] |
Move constructor in draft |
Yes |
|
|
| 1309 |
C++11 |
15.5.3.1 [utility.arg.requirements] |
Missing expressions for Move/CopyConstructible |
Yes |
|
|
| 672 |
CD1 |
15.5.3.1 [utility.arg.requirements] |
Swappable requirements need updating |
Yes |
|
|
| 594 |
Resolved |
15.5.3.1 [utility.arg.requirements] |
Disadvantages of defining Swappable in terms of CopyConstructible and Assignable |
Yes |
|
|
| 742 |
Resolved |
15.5.3.1 [utility.arg.requirements] |
Enabling swap for proxy iterators |
Yes |
|
|
| 1283 |
Resolved |
15.5.3.1 [utility.arg.requirements] |
MoveConstructible and MoveAssignable need clarification
of moved-from state |
Yes |
|
|
| 1322 |
Resolved |
15.5.3.1 [utility.arg.requirements] |
Explicit CopyConstructible requirements are insufficient |
Yes |
|
|
| 390 |
NAD Editorial |
15.5.3.1 [utility.arg.requirements] |
CopyConstructible requirements too strict |
Yes |
|
|
| 822 |
NAD |
15.5.3.1 [utility.arg.requirements] |
Object with explicit copy constructor no longer CopyConstructible |
Yes |
|
|
| 1374 |
NAD |
15.5.3.1 [utility.arg.requirements] |
Clarify moved-from objects are "toxic" |
Yes |
|
|
| 910 |
NAD Concepts |
15.5.3.1 [utility.arg.requirements] |
Effects of MoveAssignable |
Yes |
|
|
| 2152 |
LEWG |
15.5.3.2 [swappable.requirements] |
Instances of standard container types are not swappable |
Yes |
3 |
|
| 2171 |
NAD |
15.5.3.2 [swappable.requirements] |
"swappable" undefined for swapping lvalue and rvalue |
Yes |
|
|
| 2114 |
Open |
15.5.3.3 [nullablepointer.requirements] |
Incorrect "contextually convertible to bool" requirements |
Yes |
3 |
|
| 2291 |
C++14 |
15.5.3.4 [hash.requirements] |
std::hash is vulnerable to collision DoS attack |
Yes |
|
|
| 1332 |
C++11 |
15.5.3.4 [hash.requirements] |
Let Hash objects throw! |
Yes |
|
|
| 3157 |
New |
15.5.3.5 [allocator.requirements] |
Allocator destroy and fancy pointer operations must be non-throwing |
Yes |
3 |
|
| 3044 |
New |
15.5.3.5 [allocator.requirements] |
Strange specification of max_size() for an allocator |
Yes |
3 |
|
| 2461 |
New |
15.5.3.5 [allocator.requirements] |
Interaction between allocators and container exception safety guarantees |
No |
3 |
|
| 2178 |
Pending NAD Editorial |
15.5.3.5 [allocator.requirements] |
Allocator requirement changes not mentioned Annex C |
Yes |
3 |
|
| 2593 |
WP |
15.5.3.5 [allocator.requirements] |
Moved-from state of Allocators |
Yes |
4 |
|
| 2016 |
C++17 |
15.5.3.5 [allocator.requirements] |
Allocators must be no-throw swappable |
Yes |
2 |
|
| 2260 |
C++17 |
15.5.3.5 [allocator.requirements] |
Missing requirement for Allocator::pointer |
Yes |
3 |
|
| 2384 |
C++17 |
15.5.3.5 [allocator.requirements] |
Allocator's deallocate function needs better specification |
Yes |
3 |
|
| 2447 |
C++17 |
15.5.3.5 [allocator.requirements] |
Allocators and volatile-qualified value types |
Yes |
4 |
|
| 2455 |
C++17 |
15.5.3.5 [allocator.requirements] |
Allocator default construction should be allowed to throw |
Yes |
|
|
| 2466 |
C++17 |
15.5.3.5 [allocator.requirements] |
allocator_traits::max_size() default behavior is incorrect |
Yes |
3 |
|
| 2467 |
C++17 |
15.5.3.5 [allocator.requirements] |
is_always_equal has slightly inconsistent default |
Yes |
0 |
|
| 2470 |
C++17 |
15.5.3.5 [allocator.requirements] |
Allocator's destroy function should be allowed to fail to instantiate |
Yes |
|
|
| 2065 |
C++14 |
15.5.3.5 [allocator.requirements] |
Minimal allocator interface |
Yes |
|
|
| 2081 |
C++14 |
15.5.3.5 [allocator.requirements] |
Allocator requirements should include CopyConstructible |
Yes |
|
|
| 2147 |
C++14 |
15.5.3.5 [allocator.requirements] |
Unclear hint type in Allocator's allocate function |
Yes |
|
|
| 2162 |
C++14 |
15.5.3.5 [allocator.requirements] |
allocator_traits::max_size missing noexcept |
Yes |
|
|
| 2263 |
C++14 |
15.5.3.5 [allocator.requirements] |
Comparing iterators and allocator pointers with different const-character |
Yes |
1 |
|
| 752 |
C++11 |
15.5.3.5 [allocator.requirements] |
Allocator complexity requirement |
Yes |
|
|
| 258 |
CD1 |
15.5.3.5 [allocator.requirements] |
Missing allocator requirement |
Yes |
|
|
| 274 |
CD1 |
15.5.3.5 [allocator.requirements] |
a missing/impossible allocator requirement |
Yes |
|
|
| 401 |
CD1 |
15.5.3.5 [allocator.requirements] |
incorrect type casts in table 32 in lib.allocator.requirements |
Yes |
|
|
| 402 |
CD1 |
15.5.3.5 [allocator.requirements] |
wrong new expression in [some_]allocator::construct |
Yes |
|
|
| 199 |
TC1 |
15.5.3.5 [allocator.requirements] |
What does allocate(0) return? |
Yes |
|
|
| 431 |
Resolved |
15.5.3.5 [allocator.requirements] |
Swapping containers with unequal allocators |
Yes |
|
|
| 635 |
Resolved |
15.5.3.5 [allocator.requirements] |
domain of allocator::address |
Yes |
|
|
| 2108 |
Resolved |
15.5.3.5 [allocator.requirements] |
No way to identify allocator types that always compare equal |
Yes |
3 |
|
| 12 |
NAD |
15.5.3.5 [allocator.requirements] |
Way objects hold allocators unclear |
Yes |
|
|
| 197 |
NAD |
15.5.3.5 [allocator.requirements] |
max_size() underspecified |
Yes |
|
|
| 277 |
NAD |
15.5.3.5 [allocator.requirements] |
Normative encouragement in allocator requirements unclear |
Yes |
|
|
| 487 |
NAD |
15.5.3.5 [allocator.requirements] |
Allocator::construct is too limiting |
Yes |
|
|
| 560 |
NAD |
15.5.3.5 [allocator.requirements] |
User-defined allocators without default constructor |
Yes |
|
|
| 1376 |
NAD |
15.5.3.5 [allocator.requirements] |
Allocator interface is not backward compatible |
Yes |
|
|
| 2311 |
NAD |
15.5.3.5 [allocator.requirements] |
Allocator requirements should be further minimized |
Yes |
2 |
|
| 1375 |
Dup |
15.5.3.5 [allocator.requirements] |
reference_type should not have been removed from the
allocator requirements |
Yes |
|
1318 |
| 2954 |
WP |
15.5.4 [constraints] |
Specialization of the convenience variable templates should be prohibited |
Yes |
|
|
| 2139 |
WP |
15.5.4.2.1 [namespace.std] |
What is a user-defined type? |
Yes |
4 |
|
| 2129 |
C++17 |
15.5.4.2.1 [namespace.std] |
User specializations of std::initializer_list |
Yes |
3 |
|
| 1157 |
C++11 |
15.5.4.2.1 [namespace.std] |
Local types can now instantiate templates |
Yes |
|
|
| 120 |
CD1 |
15.5.4.3 [reserved.names] |
Can an implementor add specializations? |
Yes |
|
|
| 226 |
CD1 |
15.5.4.3 [reserved.names] |
User supplied specializations or overloads of namespace std function templates |
Yes |
|
|
| 232 |
CD1 |
15.5.4.3 [reserved.names] |
"depends" poorly defined in 17.4.3.1 |
Yes |
|
|
| 422 |
CD1 |
15.5.4.3 [reserved.names] |
explicit specializations of member functions of class templates |
Yes |
|
|
| 3132 |
WP |
15.5.4.3.2 [macro.names] |
Library needs to ban macros named expects or ensures |
Yes |
0 |
|
| 3147 |
WP |
15.5.4.3.2 [macro.names] |
Definitions of "likely" and "unlikely" are likely to cause problems |
Yes |
0 |
|
| 2014 |
C++11 |
15.5.4.3.2 [macro.names] |
More restrictions on macro names |
Yes |
|
|
| 294 |
CD1 |
15.5.4.3.2 [macro.names] |
User defined macros and standard headers |
Yes |
|
|
| 2340 |
C++17 |
15.5.4.6 [replacement.functions] |
Replacement allocation functions declared as inline |
Yes |
2 |
|
| 404 |
CD1 |
15.5.4.6 [replacement.functions] |
May a replacement allocation function be declared inline? |
Yes |
|
|
| 3142 |
New |
15.5.4.8 [res.on.functions] |
std::foo<incomplete> should be ill-formed NDR |
Yes |
3 |
|
| 1004 |
C++11 |
15.5.4.8 [res.on.functions] |
Clarify "throws an exception" |
Yes |
|
|
| 611 |
CD1 |
15.5.4.8 [res.on.functions] |
Standard library templates and incomplete types |
Yes |
|
|
| 2468 |
C++17 |
15.5.4.9 [res.on.arguments] |
Self-move-assignment of library types |
Yes |
2 |
|
| 1362 |
C++11 |
15.5.4.9 [res.on.arguments] |
Description of binding to rvalue-references should use the new 'xvalue' vocabulary |
Yes |
|
|
| 1204 |
C++11 |
15.5.4.9 [res.on.arguments] |
Global permission to move |
Yes |
|
|
| 2224 |
C++17 |
15.5.4.10 [res.on.objects] |
Ambiguous status of access to non-live objects |
Yes |
2 |
|
| 1095 |
C++11 |
15.5.4.10 [res.on.objects] |
Shared objects and the library wording unclear |
Yes |
|
|
| 529 |
NAD Editorial |
15.5.4.11 [res.on.required] |
The standard encourages redundant and confusing preconditions |
Yes |
|
|
| 2112 |
C++14 |
15.5.5 [conforming] |
User-defined classes that cannot be derived from |
Yes |
1 |
|
| 2891 |
NAD |
15.5.5 [conforming] |
Relax library requirements on volatile types |
Yes |
|
|
| 94 |
NAD |
15.5.5 [conforming] |
May library implementors add template parameters to Standard Library classes? |
Yes |
|
|
| 2113 |
NAD |
15.5.5 [conforming] |
Do library implementers have the freedom to add final to non-polymorphic components? |
Yes |
|
|
| 2373 |
NAD |
15.5.5 [conforming] |
Make new entities and names in namespace std conforming extensions |
Yes |
3 |
|
| 1178 |
C++11 |
15.5.5.2 [res.on.headers] |
Header dependencies |
Yes |
|
|
| 2133 |
C++17 |
15.5.5.4 [global.functions] |
Attitude to overloaded comma for iterators |
Yes |
3 |
|
| 2795 |
C++17 |
15.5.5.4 [global.functions] |
§[global.functions] provides incorrect example of ADL use |
Yes |
|
|
| 225 |
CD1 |
15.5.5.4 [global.functions] |
std:: algorithms use of other unqualified algorithms |
Yes |
|
|
| 147 |
TC1 |
15.5.5.4 [global.functions] |
Library Intro refers to global functions that aren't global |
Yes |
|
|
| 2930 |
NAD |
15.5.5.4 [global.functions] |
Are implementations allowed to split non-member functions into several overloads? |
Yes |
|
|
| 2695 |
New |
15.5.5.5 [member.functions] |
"As if" unclear in [member.functions] |
No |
3 |
|
| 2259 |
C++17 |
15.5.5.5 [member.functions] |
Issues in 17.6.5.5 rules for member functions |
Yes |
3 |
|
| 2563 |
NAD |
15.5.5.5 [member.functions] |
LWG 2259 relaxes requirements, perhaps unintentionally |
Yes |
2 |
|
| 95 |
NAD |
15.5.5.5 [member.functions] |
Members added by the implementation |
Yes |
|
|
| 2013 |
C++14 |
15.5.5.6 [constexpr.functions] |
Do library implementers have the freedom to add constexpr? |
Yes |
|
|
| 2892 |
NAD |
15.5.5.6 [constexpr.functions] |
Relax the prohibition on libraries adding constexpr |
Yes |
1 |
|
| 2044 |
C++14 |
15.5.5.7 [algorithm.stable] |
No definition of "Stable" for copy algorithms |
Yes |
|
|
| 2414 |
Open |
15.5.5.8 [reentrancy] |
Member function reentrancy should be implementation-defined |
Yes |
3 |
|
| 2382 |
Pending NAD |
15.5.5.8 [reentrancy] |
Unclear order of container update versus object destruction on removing an object |
Yes |
2 |
|
| 1526 |
Resolved |
15.5.5.9 [res.on.data.races] |
C++ should not impose thread safety requirements on C99 library implementations |
Yes |
3 |
|
| 2866 |
C++17 |
15.5.5.11 [derivation] |
Incorrect derived classes constraints |
Yes |
|
|
| 119 |
TC1 |
15.5.5.12 [res.on.exception.handling] |
Should virtual functions be allowed to strengthen the exception specification? |
Yes |
|
|
| 2867 |
Resolved |
15.5.5.12 [res.on.exception.handling] |
Bad footnote about explicit exception-specification |
Yes |
|
|
| 372 |
NAD |
15.5.5.12 [res.on.exception.handling] |
Inconsistent description of stdlib exceptions |
Yes |
|
|
| 2839 |
Open |
15.5.5.15 [lib.types.movedfrom] |
Self-move-assignment of library types, again |
Yes |
2 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 312 |
CD1 |
19 [utilities] |
Table 27 is missing headers |
Yes |
|
|
| 2888 |
Resolved |
19 [utilities] |
Variables of library tag types need to be inline variables |
Yes |
|
|
| 2889 |
Resolved |
19 [utilities] |
Mark constexpr global variables as inline |
Yes |
|
|
| 1075 |
Resolved |
19 [utilities] |
Scoped allocators are too complex |
Yes |
|
|
| 2893 |
NAD |
19 [utilities] |
Parsing Hexadecimally in P0067R4 |
Yes |
|
|
| 1289 |
Tentatively NAD |
19.2 [utility] |
Generic casting requirements for smart pointers |
Yes |
|
|
| 2212 |
C++17 |
19.2 [utility] |
tuple_size for const pair request <tuple> header |
Yes |
3 |
|
| 1255 |
C++11 |
19.2 [utility] |
declval should be added to the library |
Yes |
|
|
| 2955 |
Resolved |
19.2 [utility] |
to_chars / from_chars depend on std::string |
Yes |
|
|
| 1377 |
Resolved |
19.2 [utility] |
The revised forward is not compatible with access-control |
Yes |
|
|
| 2456 |
Resolved |
19.2 [utility] |
Incorrect exception specifications for 'swap' throughout library |
Yes |
1 |
|
| 1373 |
NAD |
19.2 [utility] |
Customizable traits should have their own headers |
Yes |
|
|
| 2153 |
LEWG |
19.2.2 [utility.swap] |
Narrowing of the non-member swap contract |
Yes |
2 |
|
| 2800 |
Resolved |
19.2.2 [utility.swap] |
constexpr swap |
Yes |
3 |
|
| 2554 |
Resolved |
19.2.2 [utility.swap] |
Swapping multidimensional arrays is never noexcept |
Yes |
2 |
|
| 2297 |
NAD |
19.2.3 [utility.exchange] |
[CD] Missing type requirements for std::exchange |
Yes |
|
|
| 2388 |
NAD |
19.2.3 [utility.exchange] |
Handling self-assignment in the proposed library function std::exchange |
Yes |
2 |
|
| 939 |
C++11 |
19.2.4 [forward] |
Problem with std::identity and reference-to-temporaries |
Yes |
|
|
| 700 |
CD1 |
19.2.4 [forward] |
N1856 defines struct identity |
Yes |
|
|
| 808 |
CD1 |
19.2.4 [forward] |
§[forward] incorrect redundant specification |
Yes |
|
|
| 823 |
Resolved |
19.2.4 [forward] |
identity<void> seems broken |
Yes |
|
|
| 1054 |
Resolved |
19.2.4 [forward] |
forward broken |
Yes |
|
|
| 2599 |
New |
19.2.6 [declval] |
Library incomplete type permission phrase is unclear |
No |
3 |
|
| 2314 |
C++14 |
19.3.1 [intseq.general] |
apply() should return decltype(auto) and use decay_t before tuple_size |
Yes |
0 |
|
| 2345 |
NAD |
19.3.2 [intseq.intseq] |
integer_sequence should have a self-typedef ::type |
Yes |
2 |
|
| 296 |
C++11 |
19.4 [pairs] |
Missing descriptions and requirements of pair operators |
Yes |
|
|
| 811 |
C++11 |
19.4 [pairs] |
pair of pointers no longer works with literal 0 |
Yes |
|
|
| 885 |
C++11 |
19.4 [pairs] |
pair assignment |
Yes |
|
|
| 265 |
CD1 |
19.4 [pairs] |
std::pair::pair() effects overly restrictive |
Yes |
|
|
| 706 |
CD1 |
19.4 [pairs] |
make_pair() should behave as make_tuple() wrt. reference_wrapper() |
Yes |
|
|
| 181 |
TC1 |
19.4 [pairs] |
make_pair() unintended behavior |
Yes |
|
|
| 353 |
Resolved |
19.4 [pairs] |
std::pair missing template assignment |
Yes |
|
|
| 482 |
Resolved |
19.4 [pairs] |
Swapping pairs |
Yes |
|
|
| 1378 |
Resolved |
19.4 [pairs] |
pair and tuple have too many conversions |
Yes |
|
|
| 1380 |
Resolved |
19.4 [pairs] |
pair and tuple of references need to better specify move-semantics |
Yes |
|
|
| 1382 |
Resolved |
19.4 [pairs] |
pair and tuple constructors should forward arguments |
Yes |
|
|
| 1383 |
Resolved |
19.4 [pairs] |
Inconsistent defaulted move/copy members in pair and tuple |
Yes |
|
|
| 840 |
NAD |
19.4 [pairs] |
pair default template argument |
Yes |
|
|
| 916 |
NAD |
19.4 [pairs] |
Redundant move-assignment operator of pair should be removed |
Yes |
|
|
| 348 |
Dup |
19.4 [pairs] |
Minor issue with std::pair operator< |
Yes |
|
532 |
| 1167 |
NAD Concepts |
19.4 [pairs] |
pair<T,U> doesn't model LessThanComparable in unconstrained code even if
T and U do. |
Yes |
|
|
| 2289 |
Open |
19.4.2 [pairs.pair] |
constexpr guarantees of defaulted functions still insufficient |
Yes |
3 |
|
| 2958 |
WP |
19.4.2 [pairs.pair] |
Moves improperly defined as deleted |
Yes |
2 |
|
| 2729 |
C++17 |
19.4.2 [pairs.pair] |
Missing SFINAE on std::pair::operator= |
Yes |
2 |
|
| 1324 |
Resolved |
19.4.2 [pairs.pair] |
Still too many implicit conversions for pair and tuple |
Yes |
|
|
| 1326 |
Resolved |
19.4.2 [pairs.pair] |
Missing/wrong preconditions for pair and tuple functions |
Yes |
|
|
| 1379 |
Resolved |
19.4.2 [pairs.pair] |
pair copy-assignment not consistent for references |
Yes |
|
|
| 2068 |
NAD |
19.4.2 [pairs.pair] |
std::pair not C++03-compatible with defaulted copy c'tor |
Yes |
|
|
| 2766 |
New |
19.4.3 [pairs.spec] |
Swapping non-swappable types |
Yes |
3 |
|
| 3166 |
New |
19.4.4 [pair.astuple] |
No such descriptive element as Value: |
No |
3 |
|
| 2974 |
WP |
19.4.4 [pair.astuple] |
Diagnose out of bounds tuple_element/variant_alternative |
Yes |
|
|
| 1061 |
NAD Editorial |
19.4.4 [pair.astuple] |
Bad indexing for tuple access to pair (Editorial?) |
Yes |
|
|
| 2899 |
Open |
19.5 [tuple] |
is_(nothrow_)move_constructible and tuple, optional and unique_ptr |
Yes |
2 |
|
| 522 |
CD1 |
19.5 [tuple] |
Tuple doesn't define swap |
Yes |
|
|
| 801 |
Resolved |
19.5 [tuple] |
tuple and pair trivial members |
Yes |
|
|
| 2773 |
C++17 |
19.5.1 [tuple.general] |
Making std::ignore constexpr |
Yes |
0 |
|
| 2796 |
C++17 |
19.5.1 [tuple.general] |
tuple should be a literal type |
Yes |
2 |
|
| 2446 |
NAD |
19.5.1 [tuple.general] |
Unspecialized std::tuple_size should be defined |
Yes |
|
|
| 1116 |
Resolved |
19.5.3 [tuple.tuple] |
Literal constructors for tuple |
Yes |
|
|
| 2051 |
Resolved |
19.5.3 [tuple.tuple] |
Explicit tuple constructors for more than one parameter |
Yes |
2 |
|
| 1077 |
NAD Editorial |
19.5.3 [tuple.tuple] |
Nonesense tuple declarations |
Yes |
|
|
| 3158 |
New |
19.5.3.1 [tuple.cnstr] |
tuple(allocator_arg_t, const Alloc&) should be conditionally explicit |
Yes |
3 |
|
| 2528 |
New |
19.5.3.1 [tuple.cnstr] |
Order of std::tuple construction unspecified |
No |
3 |
|
| 3121 |
Open |
19.5.3.1 [tuple.cnstr] |
tuple constructor constraints for UTypes&&... overloads |
Yes |
2 |
|
| 3155 |
Open |
19.5.3.1 [tuple.cnstr] |
tuple<any, any>{allocator_arg_t, an_allocator} |
Yes |
3 |
|
| 2312 |
C++17 |
19.5.3.1 [tuple.cnstr] |
tuple's constructor constraints need to be phrased more precisely |
Yes |
2 |
|
| 2549 |
C++17 |
19.5.3.1 [tuple.cnstr] |
Tuple EXPLICIT constructor templates that take tuple parameters end up taking references
to temporaries and will create dangling references |
Yes |
2 |
|
| 886 |
C++11 |
19.5.3.1 [tuple.cnstr] |
tuple construction |
Yes |
|
|
| 807 |
CD1 |
19.5.3.1 [tuple.cnstr] |
tuple construction should not fail unless its element's construction fails |
Yes |
|
|
| 2419 |
Resolved |
19.5.3.1 [tuple.cnstr] |
Clang's libc++ extension to std::tuple |
Yes |
|
|
| 1117 |
Resolved |
19.5.3.1 [tuple.cnstr] |
tuple copy constructor |
Yes |
|
|
| 917 |
NAD |
19.5.3.1 [tuple.cnstr] |
Redundant move-assignment operator of tuple should be removed |
Yes |
|
|
| 918 |
NAD Concepts |
19.5.3.3 [tuple.swap] |
Swap for tuple needs to be conceptualized |
Yes |
|
|
| 2933 |
New |
19.5.3.4 [tuple.creation] |
PR for LWG 2773 could be clearer |
Yes |
3 |
|
| 2275 |
C++14 |
19.5.3.4 [tuple.creation] |
[CD] Why is forward_as_tuple not constexpr? |
Yes |
|
|
| 2301 |
C++14 |
19.5.3.4 [tuple.creation] |
Why is std::tie not constexpr? |
Yes |
2 |
|
| 1384 |
C++11 |
19.5.3.4 [tuple.creation] |
Function pack_arguments is poorly named |
Yes |
|
|
| 1385 |
C++11 |
19.5.3.4 [tuple.creation] |
tuple_cat should be a single variadic signature |
Yes |
|
|
| 1386 |
C++11 |
19.5.3.4 [tuple.creation] |
pack_arguments overly complex |
Yes |
|
|
| 1201 |
Resolved |
19.5.3.4 [tuple.creation] |
Do we always want to unwrap ref-wrappers in make_tuple |
Yes |
|
|
| 2770 |
C++17 |
19.5.3.6 [tuple.helper] |
tuple_size<const T> specialization is not SFINAE compatible and breaks decomposition declarations |
Yes |
1 |
|
| 2313 |
C++14 |
19.5.3.6 [tuple.helper] |
tuple_size should always derive from integral_constant<size_t, N> |
Yes |
2 |
|
| 1118 |
C++11 |
19.5.3.6 [tuple.helper] |
tuple query APIs do not support cv-qualification |
Yes |
|
|
| 775 |
CD1 |
19.5.3.6 [tuple.helper] |
Tuple indexing should be unsigned? |
Yes |
|
|
| 1119 |
NAD |
19.5.3.6 [tuple.helper] |
tuple query APIs do not support references |
Yes |
|
|
| 2485 |
C++17 |
19.5.3.7 [tuple.elem] |
get() should be overloaded for const tuple&& |
Yes |
1 |
|
| 1191 |
C++11 |
19.5.3.7 [tuple.elem] |
tuple get API should respect rvalues |
Yes |
|
|
| 2472 |
New |
19.5.3.8 [tuple.rel] |
Heterogeneous comparisons in the standard library can result in ambiguities |
No |
3 |
|
| 532 |
LEWG |
19.5.3.8 [tuple.rel] |
Tuple comparison |
Yes |
|
348 |
| 1335 |
C++11 |
19.5.3.8 [tuple.rel] |
Insufficient requirements for tuple::operator<() |
Yes |
|
|
| 928 |
NAD Concepts |
19.5.3.8 [tuple.rel] |
Wrong concepts used for tuple's comparison operators |
Yes |
|
|
| 2857 |
C++17 |
19.6 [optional] |
{variant,optional,any}::emplace should return the constructed value |
Yes |
1 |
|
| 2862 |
Resolved |
19.6 [optional] |
LWG 2756 should be accepted |
Yes |
|
|
| 2746 |
New |
19.6.3 [optional.optional] |
Inconsistency between requirements for emplace between optional and variant |
No |
3 |
|
| 2990 |
Open |
19.6.3 [optional.optional] |
optional::value_type is not always a value type |
Yes |
3 |
|
| 2825 |
LEWG |
19.6.3 [optional.optional] |
LWG 2756 breaks class template argument deduction for optional |
No |
2 |
|
| 2756 |
C++17 |
19.6.3 [optional.optional] |
C++ WP optional<T> should 'forward' T's implicit conversions |
Yes |
1 |
|
| 2900 |
C++17 |
19.6.3 [optional.optional] |
The copy and move constructors of optional are not constexpr |
Yes |
|
|
| 3016 |
NAD |
19.6.3 [optional.optional] |
optional and over-aligned types |
Yes |
3 |
|
| 2811 |
New |
19.6.3.1 [optional.ctor] |
"Selected constructor" wording is incorrect for optional/variant/any |
No |
3 |
|
| 2842 |
C++17 |
19.6.3.1 [optional.ctor] |
in_place_t check for optional::optional(U&&) should decay U |
Yes |
0 |
|
| 2753 |
Resolved |
19.6.3.1 [optional.ctor] |
Optional's constructors and assignments need constraints |
Yes |
0 |
|
| 2748 |
C++17 |
19.6.3.4 [optional.swap] |
swappable traits for optionals |
Yes |
0 |
|
| 2829 |
Open |
19.6.3.5 [optional.observe] |
LWG 2740 leaves behind vacuous words |
No |
2 |
|
| 2740 |
C++17 |
19.6.3.5 [optional.observe] |
constexpr optional<T>::operator-> |
Yes |
0 |
|
| 2736 |
C++17 |
19.6.4 [optional.nullopt] |
nullopt_t insufficiently constrained |
Yes |
2 |
|
| 2806 |
C++17 |
19.6.5 [optional.bad.access] |
Base class of bad_optional_access |
Yes |
1 |
|
| 2945 |
WP |
19.6.8 [optional.comp_with_t] |
Order of template parameters in optional comparisons |
Yes |
2 |
|
| 2934 |
C++17 |
19.6.8 [optional.comp_with_t] |
optional<const T> doesn't compare with T |
Yes |
|
|
| 2805 |
Resolved |
19.7 [variant] |
void and reference type alternatives in variant, variant<> and
index() |
Yes |
|
|
| 2881 |
New |
19.7.3 [variant.variant] |
Adopt section III of P0308R0 |
No |
3 |
|
| 2901 |
C++17 |
19.7.3 [variant.variant] |
Variants cannot properly support allocators |
Yes |
0 |
|
| 2902 |
NAD |
19.7.3 [variant.variant] |
variant should only support complete types |
Yes |
0 |
|
| 2971 |
NAD |
19.7.3 [variant.variant] |
variant should require Destructible types |
Yes |
|
|
| 2833 |
Open |
19.7.3.1 [variant.ctor] |
Library needs to specify what it means when it declares a function constexpr |
Yes |
2 |
|
| 2991 |
LEWG |
19.7.3.1 [variant.ctor] |
variant copy constructor missing noexcept(see below) |
Yes |
|
|
| 3024 |
WP |
19.7.3.1 [variant.ctor] |
variant's copies must be deleted instead of disabled via SFINAE |
Yes |
|
|
| 2903 |
C++17 |
19.7.3.1 [variant.ctor] |
The form of initialization for the emplace-constructors is not specified |
Yes |
|
|
| 2882 |
Resolved |
19.7.3.1 [variant.ctor] |
Clarify variant construction |
Yes |
|
|
| 3069 |
New |
19.7.3.3 [variant.assign] |
Move assigning variant's subobject corrupts data |
Yes |
3 |
|
| 2904 |
C++17 |
19.7.3.3 [variant.assign] |
Make variant move-assignment more exception safe |
Yes |
|
|
| 2749 |
C++17 |
19.7.3.6 [variant.swap] |
swappable traits for variants |
Yes |
1 |
|
| 3052 |
LEWG |
19.7.7 [variant.visit] |
visit is underconstrained |
Yes |
2 |
|
| 2970 |
WP |
19.7.7 [variant.visit] |
Return type of std::visit misspecified |
Yes |
2 |
|
| 2809 |
Resolved |
19.7.12 [variant.hash] |
variant hash requirements |
Yes |
|
|
| 2868 |
C++17 |
19.8.2 [any.bad_any_cast] |
Missing specification of bad_any_cast::what() |
Yes |
|
|
| 2789 |
C++17 |
19.8.3 [any.class] |
Equivalence of contained objects |
Yes |
0 |
|
| 2744 |
C++17 |
19.8.3.1 [any.cons] |
any's in_place constructors |
Yes |
0 |
|
| 2754 |
Resolved |
19.8.3.1 [any.cons] |
The in_place constructors and emplace functions added by P0032R3 don't require CopyConstructible |
Yes |
1 |
|
| 2886 |
NAD |
19.8.3.4 [any.observers] |
Keep the empty() functions in any |
Yes |
|
|
| 2768 |
C++17 |
19.8.4 [any.nonmembers] |
any_cast and move semantics |
Yes |
0 |
|
| 2769 |
C++17 |
19.8.4 [any.nonmembers] |
Redundant const in the return type of any_cast(const any&) |
Yes |
0 |
|
| 2348 |
Open |
19.9.2 [template.bitset] |
charT('1') is not the wide equivalent of '1' |
Yes |
3 |
|
| 853 |
C++11 |
19.9.2 [template.bitset] |
to_string needs updating with zero and one |
Yes |
|
|
| 1113 |
C++11 |
19.9.2 [template.bitset] |
bitset::to_string could be simplified |
Yes |
|
|
| 1227 |
C++11 |
19.9.2 [template.bitset] |
<bitset> synopsis overspecified |
Yes |
|
|
| 1250 |
C++11 |
19.9.2 [template.bitset] |
<bitset> still overspecified |
Yes |
|
|
| 693 |
CD1 |
19.9.2 [template.bitset] |
std::bitset::all() missing |
Yes |
|
|
| 694 |
CD1 |
19.9.2 [template.bitset] |
std::bitset and long long |
Yes |
|
|
| 11 |
TC1 |
19.9.2 [template.bitset] |
Bitset minor problems |
Yes |
|
|
| 1112 |
NAD |
19.9.2 [template.bitset] |
bitsets and new style for loop |
Yes |
|
|
| 116 |
Dup |
19.9.2 [template.bitset] |
bitset cannot be constructed with a const char* |
Yes |
|
778 |
| 2250 |
C++17 |
19.9.2.1 [bitset.cons] |
Follow-up On Library Issue 2207 |
Yes |
3 |
|
| 1325 |
C++11 |
19.9.2.1 [bitset.cons] |
bitset |
Yes |
|
|
| 396 |
CD1 |
19.9.2.1 [bitset.cons] |
what are characters zero and one |
Yes |
|
|
| 457 |
CD1 |
19.9.2.1 [bitset.cons] |
bitset constructor: incorrect number of initialized bits |
Yes |
|
|
| 778 |
CD1 |
19.9.2.1 [bitset.cons] |
std::bitset does not have any constructor taking a string literal |
Yes |
|
116 |
| 907 |
C++11 |
19.9.2.2 [bitset.members] |
Bitset's immutable element retrieval is inconsistently defined |
Yes |
|
|
| 186 |
CD1 |
19.9.2.2 [bitset.members] |
bitset::set() second parameter should be bool |
Yes |
|
|
| 434 |
CD1 |
19.9.2.2 [bitset.members] |
bitset::to_string() hard to use |
Yes |
|
|
| 1168 |
NAD Editorial |
19.9.2.2 [bitset.members] |
Odd wording for bitset equality operators |
Yes |
|
|
| 303 |
CD1 |
19.9.4 [bitset.operators] |
Bitset input operator underspecified |
Yes |
|
|
| 1073 |
C++11 |
19.10 [memory] |
Declaration of allocator_arg should be constexpr |
Yes |
|
|
| 1401 |
C++11 |
19.10 [memory] |
Provide support for unique_ptr<T> == nullptr |
Yes |
|
|
| 1402 |
C++11 |
19.10 [memory] |
nullptr constructors for smart pointers should be constexpr |
Yes |
|
|
| 1233 |
NAD Editorial |
19.10 [memory] |
Missing unique_ptr signatures in synopsis |
Yes |
|
|
| 1026 |
NAD Concepts |
19.10 [memory] |
Smart pointers need to be concept-constrained templates |
Yes |
|
|
| 1404 |
C++11 |
19.10.3 [pointer.traits] |
pointer_traits should have a size_type member |
Yes |
|
|
| 1098 |
C++11 |
19.10.5 [util.dynamic.safety] |
definition of get_pointer_safety() |
Yes |
|
|
| 1408 |
C++11 |
19.10.5 [util.dynamic.safety] |
Allow recycling of pointers after undeclare_no_pointers |
Yes |
|
|
| 858 |
CD1 |
19.10.5 [util.dynamic.safety] |
Wording for Minimal Support for Garbage Collection |
Yes |
|
|
| 1022 |
NAD Editorial |
19.10.5 [util.dynamic.safety] |
Pointer-safety API has nothing to do with smart pointers |
Yes |
|
|
| 2421 |
New |
19.10.6 [ptr.align] |
Non-specification of handling zero size in std::align [ptr.align] |
No |
3 |
|
| 2377 |
C++17 |
19.10.6 [ptr.align] |
std::align requirements overly strict |
Yes |
0 |
|
| 1403 |
C++11 |
19.10.7 [allocator.tag] |
Inconsistent definitions for allocator_arg |
Yes |
|
|
| 2284 |
C++14 |
19.10.9 [allocator.traits] |
Inconsistency in allocator_traits::max_size |
Yes |
|
|
| 1318 |
NAD |
19.10.9.1 [allocator.traits.types] |
N2982 removes previous allocator capabilities |
Yes |
|
1375 |
| 1285 |
C++11 |
19.10.9.2 [allocator.traits.members] |
allocator_traits call to new |
Yes |
|
|
| 1286 |
C++11 |
19.10.9.2 [allocator.traits.members] |
allocator_traits::select_on_container_copy_construction type-o |
Yes |
|
|
| 3035 |
WP |
19.10.10 [default.allocator] |
std::allocator's constructors should be constexpr |
Yes |
0 |
|
| 2103 |
C++14 |
19.10.10 [default.allocator] |
std::allocator_traits<std::allocator<T>>::propagate_on_container_move_assignment |
Yes |
|
|
| 1027 |
NAD Concepts |
19.10.10 [default.allocator] |
std::allocator needs to be a concept-constrained template |
Yes |
|
|
| 2089 |
EWG |
19.10.10.1 [allocator.members] |
std::allocator::construct should use uniform initialization |
Yes |
2 |
|
| 234 |
CD1 |
19.10.10.1 [allocator.members] |
Typos in allocator definition |
Yes |
|
|
| 400 |
CD1 |
19.10.10.1 [allocator.members] |
redundant type cast in lib.allocator.members |
Yes |
|
|
| 578 |
CD1 |
19.10.10.1 [allocator.members] |
purpose of hint to allocator::allocate() |
Yes |
|
|
| 634 |
CD1 |
19.10.10.1 [allocator.members] |
allocator.address() doesn't work for types overloading operator& |
Yes |
|
350 |
| 350 |
Dup |
19.10.10.1 [allocator.members] |
allocator<>::address |
Yes |
|
634 |
| 3156 |
New |
19.10.11 [specialized.algorithms] |
ForwardIterator should only mean forward iterator |
Yes |
3 |
|
| 3063 |
New |
19.10.11 [specialized.algorithms] |
Parallel algorithms in <memory> are underspecified |
No |
3 |
|
| 3064 |
New |
19.10.11 [specialized.algorithms] |
How do uninitialized memory algorithms obtain pointer without undefined behavior? |
No |
3 |
|
| 2433 |
C++17 |
19.10.11 [specialized.algorithms] |
uninitialized_copy()/etc. should tolerate overloaded operator& |
Yes |
0 |
|
| 866 |
C++11 |
19.10.11 [specialized.algorithms] |
Qualification of placement new-expressions |
Yes |
|
|
| 999 |
C++11 |
19.10.11 [specialized.algorithms] |
Taking the address of a function |
Yes |
|
|
| 1029 |
NAD Concepts |
19.10.11 [specialized.algorithms] |
Specialized algorithms for memory management need to be concept-constrained templates |
Yes |
|
|
| 2296 |
C++17 |
19.10.11.2 [specialized.addressof] |
std::addressof should be constexpr |
Yes |
3 |
|
| 2598 |
C++17 |
19.10.11.2 [specialized.addressof] |
addressof works on temporaries |
Yes |
3 |
|
| 970 |
C++11 |
19.10.11.2 [specialized.addressof] |
addressof overload unneeded |
Yes |
|
|
| 3054 |
WP |
19.10.11.5 [uninitialized.copy] |
uninitialized_copy appears to not be able to meet its exception-safety guarantee |
Yes |
2 |
|
| 754 |
NAD Editorial |
19.10.11.5 [uninitialized.copy] |
Ambiguous return clause for std::uninitialized_copy |
Yes |
|
|
| 582 |
NAD |
19.10.11.5 [uninitialized.copy] |
specialized algorithms and volatile storage |
Yes |
|
|
| 1339 |
C++11 |
19.10.11.7 [uninitialized.fill] |
uninitialized_fill_n should return the end of its range |
Yes |
|
|
| 2948 |
WP |
19.11.1 [unique.ptr] |
unique_ptr does not define operator<< for stream output |
Yes |
0 |
|
| 673 |
CD1 |
19.11.1 [unique.ptr] |
unique_ptr update |
Yes |
|
|
| 740 |
CD1 |
19.11.1 [unique.ptr] |
Please remove *_ptr<T[N]> |
Yes |
|
|
| 762 |
CD1 |
19.11.1 [unique.ptr] |
std::unique_ptr requires complete type? |
Yes |
|
|
| 1193 |
C++11 |
19.11.1.1 [unique.ptr.dltr] |
default_delete cannot be instantiated with incomplete types |
Yes |
|
|
| 854 |
C++11 |
19.11.1.1.2 [unique.ptr.dltr.dflt] |
default_delete converting constructor underspecified |
Yes |
|
|
| 1517 |
C++11 |
19.11.1.1.2 [unique.ptr.dltr.dflt] |
default_delete's default constructor should be trivial |
Yes |
|
|
| 938 |
C++11 |
19.11.1.1.3 [unique.ptr.dltr.dflt1] |
default_delete<T[]>::operator() should only accept T* |
Yes |
|
|
| 3159 |
New |
19.11.1.2 [unique.ptr.single] |
§[unique.ptr.single] requirements on deleter may be too strict |
No |
3 |
|
| 2262 |
Open |
19.11.1.2 [unique.ptr.single] |
Requirement for unique_ptr<T>::get_deleter()(p) to be able to destroy the unique_ptr |
Yes |
3 |
|
| 2361 |
C++17 |
19.11.1.2 [unique.ptr.single] |
Apply 2299 resolution throughout library |
Yes |
|
|
| 1303 |
C++11 |
19.11.1.2 [unique.ptr.single] |
shared_ptr, unique_ptr, and rvalue references v2 |
Yes |
|
|
| 834 |
Resolved |
19.11.1.2 [unique.ptr.single] |
unique_ptr::pointer requirements underspecified |
Yes |
|
|
| 983 |
Resolved |
19.11.1.2 [unique.ptr.single] |
unique_ptr reference deleters should not be moved from |
Yes |
|
|
| 2944 |
WP |
19.11.1.2.1 [unique.ptr.single.ctor] |
LWG 2905 accidentally removed requirement that construction of the deleter doesn't throw an exception |
Yes |
0 |
|
| 2801 |
C++17 |
19.11.1.2.1 [unique.ptr.single.ctor] |
Default-constructibility of unique_ptr |
Yes |
2 |
|
| 2905 |
C++17 |
19.11.1.2.1 [unique.ptr.single.ctor] |
is_constructible_v<unique_ptr<P, D>, P, D const &> should be false when
D is not copy constructible |
Yes |
|
|
| 932 |
Resolved |
19.11.1.2.1 [unique.ptr.single.ctor] |
unique_ptr(pointer p) for pointer deleter types |
Yes |
|
|
| 950 |
Resolved |
19.11.1.2.1 [unique.ptr.single.ctor] |
unique_ptr converting ctor shouldn't accept array form |
Yes |
|
|
| 1100 |
Resolved |
19.11.1.2.1 [unique.ptr.single.ctor] |
auto_ptr to unique_ptr conversion |
Yes |
|
|
| 3164 |
NAD |
19.11.1.2.1 [unique.ptr.single.ctor] |
Unhelpful "shall not participate" constraints for unique_ptr with reference deleter |
Yes |
|
|
| 2047 |
C++14 |
19.11.1.2.3 [unique.ptr.single.asgn] |
Incorrect "mixed" move-assignment semantics of unique_ptr |
Yes |
|
|
| 2246 |
C++14 |
19.11.1.2.3 [unique.ptr.single.asgn] |
unique_ptr assignment effects w.r.t. deleter |
Yes |
|
|
| 1021 |
C++11 |
19.11.1.2.3 [unique.ptr.single.asgn] |
Allow nullptr_t assignments to unique_ptr |
Yes |
|
|
| 2228 |
Resolved |
19.11.1.2.3 [unique.ptr.single.asgn] |
Missing SFINAE rule in unique_ptr templated assignment |
Yes |
3 |
|
| 2762 |
Open |
19.11.1.2.4 [unique.ptr.single.observers] |
unique_ptr operator*() should be noexcept |
Yes |
3 |
|
| 686 |
NAD |
19.11.1.2.4 [unique.ptr.single.observers] |
unique_ptr and shared_ptr fail to specify non-convertibility to int for unspecified-bool-type |
Yes |
|
|
| 998 |
C++11 |
19.11.1.2.5 [unique.ptr.single.modifiers] |
Smart pointer referencing its owner |
Yes |
|
|
| 806 |
CD1 |
19.11.1.2.5 [unique.ptr.single.modifiers] |
unique_ptr::reset effects incorrect, too permissive |
Yes |
|
|
| 933 |
NAD |
19.11.1.2.5 [unique.ptr.single.modifiers] |
Unique_ptr defect |
Yes |
|
|
| 2118 |
Resolved |
19.11.1.3 [unique.ptr.runtime] |
[CD] unique_ptr for array does not support cv qualification conversion of actual argument |
Yes |
1 |
|
| 1293 |
Resolved |
19.11.1.3 [unique.ptr.runtime] |
unique_ptr<T[], D> needs to get rid of unspecified-pointer-type |
Yes |
|
|
| 2060 |
NAD Editorial |
19.11.1.3 [unique.ptr.runtime] |
unique_ptr<T[]>(nullptr_t) missing noexcept |
Yes |
|
|
| 2520 |
C++17 |
19.11.1.3.1 [unique.ptr.runtime.ctor] |
N4089 broke initializing unique_ptr<T[]> from a nullptr |
Yes |
2 |
|
| 2169 |
C++14 |
19.11.1.3.4 [unique.ptr.runtime.modifiers] |
Missing reset() requirements in unique_ptr specialization |
Yes |
|
|
| 821 |
C++11 |
19.11.1.3.4 [unique.ptr.runtime.modifiers] |
Minor cleanup : unique_ptr |
Yes |
|
|
| 1297 |
Resolved |
19.11.1.5 [unique.ptr.special] |
unique_ptr's relational operator functions should induce a total order |
Yes |
|
|
| 2376 |
C++17 |
19.11.2 [util.smartptr.weak.bad] |
bad_weak_ptr::what() overspecified |
Yes |
|
|
| 1406 |
Tentatively NAD |
19.11.3 [util.smartptr.shared] |
Support hashing smart-pointers based on owner |
Yes |
|
|
| 3018 |
New |
19.11.3 [util.smartptr.shared] |
shared_ptr of function type |
Yes |
3 |
|
| 2594 |
New |
19.11.3 [util.smartptr.shared] |
Contradicting definition of empty shared_ptr on shared_ptr(nullptr, d) |
Yes |
3 |
|
| 2996 |
WP |
19.11.3 [util.smartptr.shared] |
Missing rvalue overloads for shared_ptr operations |
Yes |
|
|
| 2365 |
C++17 |
19.11.3 [util.smartptr.shared] |
Missing noexcept in shared_ptr::shared_ptr(nullptr_t) |
Yes |
|
|
| 2411 |
C++17 |
19.11.3 [util.smartptr.shared] |
shared_ptr is only contextually convertible to bool |
Yes |
0 |
|
| 2873 |
C++17 |
19.11.3 [util.smartptr.shared] |
Add noexcept to several shared_ptr related functions |
Yes |
|
|
| 758 |
C++11 |
19.11.3 [util.smartptr.shared] |
shared_ptr and nullptr |
Yes |
|
|
| 896 |
C++11 |
19.11.3 [util.smartptr.shared] |
Library thread safety issue |
Yes |
|
|
| 541 |
CD1 |
19.11.3 [util.smartptr.shared] |
shared_ptr template assignment and void |
Yes |
|
|
| 674 |
CD1 |
19.11.3 [util.smartptr.shared] |
shared_ptr interface changes for consistency with N1856 |
Yes |
|
|
| 710 |
CD1 |
19.11.3 [util.smartptr.shared] |
Missing postconditions |
Yes |
|
|
| 813 |
CD1 |
19.11.3 [util.smartptr.shared] |
"empty" undefined for shared_ptr |
Yes |
|
|
| 2864 |
Resolved |
19.11.3 [util.smartptr.shared] |
Merge shared_ptr changes from Library Fundamentals to C++17 |
Yes |
|
|
| 2810 |
Resolved |
19.11.3 [util.smartptr.shared] |
use_count and unique in shared_ptr |
Yes |
|
|
| 1031 |
NAD |
19.11.3 [util.smartptr.shared] |
Need shared_ptr conversion to a unique_ptr |
Yes |
|
|
| 2906 |
New |
19.11.3.1 [util.smartptr.shared.const] |
There is no ability to supply an allocator for the control block when constructing a shared_ptr from a
unique_ptr |
No |
3 |
|
| 2399 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr's constructor from unique_ptr should be constrained |
Yes |
0 |
|
| 2415 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
Inconsistency between unique_ptr and shared_ptr |
Yes |
2 |
|
| 2495 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
There is no such thing as an Exception Safety element |
Yes |
0 |
|
| 2685 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr deleters must not not throw on move construction |
Yes |
0 |
|
| 2802 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr constructor requirements for a deleter |
Yes |
2 |
|
| 2874 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
Constructor shared_ptr::shared_ptr(Y*) should be constrained |
Yes |
|
|
| 2875 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr::shared_ptr(Y*, D, […]) constructors should be constrained |
Yes |
|
|
| 2876 |
C++17 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr::shared_ptr(const weak_ptr<Y>&) constructor should be constrained |
Yes |
|
|
| 881 |
C++11 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr conversion issue |
Yes |
|
|
| 925 |
C++11 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr's explicit conversion from unique_ptr |
Yes |
|
|
| 687 |
CD1 |
19.11.3.1 [util.smartptr.shared.const] |
shared_ptr conversion constructor not constrained |
Yes |
|
|
| 827 |
Resolved |
19.11.3.1 [util.smartptr.shared.const] |
constexpr shared_ptr::shared_ptr()? |
Yes |
|
|
| 1407 |
Resolved |
19.11.3.1 [util.smartptr.shared.const] |
Synch shared_ptr constructors taking movable types |
Yes |
|
|
| 2751 |
New |
19.11.3.2 [util.smartptr.shared.dest] |
shared_ptr deleter not specified to observe expired weak_ptr instances |
No |
4 |
|
| 899 |
C++11 |
19.11.3.2 [util.smartptr.shared.dest] |
Adjusting shared_ptr for nullptr_t |
Yes |
|
|
| 575 |
CD1 |
19.11.3.2 [util.smartptr.shared.dest] |
the specification of ~shared_ptr is MT-unfriendly, makes implementation assumptions |
Yes |
|
|
| 2907 |
NAD |
19.11.3.2 [util.smartptr.shared.dest] |
Semantics for destroying the deleter and the control-block of a shared_ptr are unclear |
Yes |
|
|
| 884 |
Resolved |
19.11.3.4 [util.smartptr.shared.mod] |
shared_ptr swap |
Yes |
|
|
| 2434 |
C++17 |
19.11.3.5 [util.smartptr.shared.obs] |
shared_ptr::use_count() is efficient |
Yes |
0 |
|
| 2572 |
C++17 |
19.11.3.5 [util.smartptr.shared.obs] |
The remarks for shared_ptr::operator* should apply to cv-qualified void as well |
Yes |
0 |
|
| 711 |
C++11 |
19.11.3.5 [util.smartptr.shared.obs] |
Contradiction in empty shared_ptr |
Yes |
|
|
| 540 |
CD1 |
19.11.3.5 [util.smartptr.shared.obs] |
shared_ptr<void>::operator*() |
Yes |
|
|
| 542 |
CD1 |
19.11.3.5 [util.smartptr.shared.obs] |
shared_ptr observers |
Yes |
|
|
| 2776 |
Resolved |
19.11.3.5 [util.smartptr.shared.obs] |
shared_ptr unique() and use_count() |
Yes |
2 |
|
| 2337 |
NAD |
19.11.3.5 [util.smartptr.shared.obs] |
shared_ptr operator*() should not be noexcept |
Yes |
2 |
|
| 3008 |
WP |
19.11.3.6 [util.smartptr.shared.create] |
make_shared (sub)object destruction semantics are not specified |
Yes |
2 |
|
| 3005 |
WP |
19.11.3.6 [util.smartptr.shared.create] |
Destruction order of arrays by make_shared/allocate_shared only recommended? |
Yes |
0 |
|
| 3007 |
WP |
19.11.3.6 [util.smartptr.shared.create] |
allocate_shared should rebind allocator to cv-unqualified value_type for construction |
Yes |
0 |
|
| 2696 |
C++17 |
19.11.3.6 [util.smartptr.shared.create] |
Interaction between make_shared and enable_shared_from_this is underspecified |
Yes |
2 |
|
| 2070 |
Resolved |
19.11.3.6 [util.smartptr.shared.create] |
allocate_shared should use allocator_traits<A>::construct |
Yes |
2 |
|
| 2908 |
C++17 |
19.11.3.7 [util.smartptr.shared.cmp] |
The less-than operator for shared pointers could do more |
Yes |
|
|
| 1262 |
C++11 |
19.11.3.7 [util.smartptr.shared.cmp] |
std::less<std::shared_ptr<T>> is underspecified |
Yes |
|
|
| 743 |
CD1 |
19.11.3.8 [util.smartptr.shared.spec] |
rvalue swap for shared_ptr |
Yes |
|
|
| 2964 |
WP |
19.11.3.9 [util.smartptr.shared.cast] |
Apparently redundant requirement for dynamic_pointer_cast |
Yes |
0 |
|
| 2877 |
Resolved |
19.11.3.9 [util.smartptr.shared.cast] |
Strengthen meaning of "empty shared_ptr<T>" in dynamic_pointer_cast |
Yes |
|
|
| 2400 |
C++17 |
19.11.3.10 [util.smartptr.getdeleter] |
shared_ptr's get_deleter() should use addressof() |
Yes |
0 |
|
| 533 |
CD1 |
19.11.3.10 [util.smartptr.getdeleter] |
typo in 2.2.3.10/1 |
Yes |
|
|
| 545 |
CD1 |
19.11.3.10 [util.smartptr.getdeleter] |
When is a deleter deleted? |
Yes |
|
|
| 741 |
NAD |
19.11.3.10 [util.smartptr.getdeleter] |
Const-incorrect get_deleter function for shared_ptr |
Yes |
|
|
| 3001 |
WP |
19.11.4 [util.smartptr.weak] |
weak_ptr::element_type needs remove_extent_t |
Yes |
0 |
|
| 2083 |
C++14 |
19.11.4 [util.smartptr.weak] |
const-qualification on weak_ptr::owner_before |
Yes |
|
|
| 2315 |
C++14 |
19.11.4 [util.smartptr.weak] |
weak_ptr should be movable |
Yes |
2 |
|
| 1256 |
C++11 |
19.11.4 [util.smartptr.weak] |
weak_ptr comparison functions should be removed |
Yes |
|
|
| 2942 |
WP |
19.11.4.5 [util.smartptr.weak.obs] |
LWG 2873's resolution missed weak_ptr::owner_before |
Yes |
|
|
| 2316 |
C++14 |
19.11.4.5 [util.smartptr.weak.obs] |
weak_ptr::lock() should be atomic |
Yes |
0 |
|
| 1231 |
C++11 |
19.11.4.5 [util.smartptr.weak.obs] |
weak_ptr comparisons incompletely resolved |
Yes |
|
|
| 949 |
C++11 |
19.11.5 [util.smartptr.ownerless] |
owner_less |
Yes |
|
|
| 2179 |
Resolved |
19.11.6 [util.smartptr.enab] |
enable_shared_from_this and construction from raw pointers |
Yes |
3 |
|
| 2529 |
Resolved |
19.11.6 [util.smartptr.enab] |
Assigning to enable_shared_from_this::__weak_this twice |
Yes |
3 |
|
| 2700 |
NAD |
19.12 [mem.res] |
resource_adaptor went missing |
Yes |
1 |
|
| 2724 |
C++17 |
19.12.2 [mem.res.class] |
The protected virtual member functions of memory_resource should be private |
Yes |
4 |
|
| 2843 |
WP |
19.12.2.2 [mem.res.private] |
Unclear behavior of std::pmr::memory_resource::do_allocate() |
Yes |
3 |
|
| 2701 |
NAD Editorial |
19.12.2.2 [mem.res.private] |
Unclear requirement in [memory.resource.private] |
Yes |
3 |
|
| 3036 |
New |
19.12.3 [mem.poly.allocator.class] |
polymorphic_allocator::destroy is extraneous |
Yes |
3 |
|
| 3037 |
WP |
19.12.3 [mem.poly.allocator.class] |
polymorphic_allocator and incomplete types |
Yes |
2 |
|
| 3113 |
New |
19.12.3.2 [mem.poly.allocator.mem] |
polymorphic_allocator::construct() should more closely match scoped_allocator_adaptor::construct() |
Yes |
3 |
|
| 3038 |
WP |
19.12.3.2 [mem.poly.allocator.mem] |
polymorphic_allocator::allocate should not allow integer overflow to create vulnerabilities |
Yes |
2 |
|
| 2969 |
WP |
19.12.3.2 [mem.poly.allocator.mem] |
polymorphic_allocator::construct() shouldn't pass resource() |
Yes |
2 |
|
| 2975 |
WP |
19.12.3.2 [mem.poly.allocator.mem] |
Missing case for pair construction in scoped and polymorphic allocators |
Yes |
3 |
|
| 2961 |
WP |
19.12.4 [mem.res.global] |
Bad postcondition for set_default_resource |
Yes |
|
|
| 2848 |
New |
19.12.5.2 [mem.res.pool.options] |
Pass-through threshold for pool allocator |
No |
3 |
|
| 3143 |
New |
19.12.6 [mem.res.monotonic.buffer] |
monotonic_buffer_resource growth policy is unclear |
No |
|
|
| 3120 |
Open |
19.12.6.2 [mem.res.monotonic.buffer.mem] |
Unclear behavior of monotonic_buffer_resource::release() |
Yes |
2 |
|
| 3000 |
WP |
19.12.6.2 [mem.res.monotonic.buffer.mem] |
monotonic_memory_resource::do_is_equal uses dynamic_cast unnecessarily |
Yes |
0 |
|
| 1316 |
C++11 |
19.13 [allocator.adaptor] |
scoped_allocator_adaptor operator== has no definition |
Yes |
|
|
| 1405 |
Resolved |
19.13 [allocator.adaptor] |
Move scoped_allocator_adaptor into separate header |
Yes |
|
|
| 2476 |
C++17 |
19.13.1 [allocator.adaptor.syn] |
scoped_allocator_adaptor is not assignable |
Yes |
0 |
|
| 2782 |
C++17 |
19.13.3 [allocator.adaptor.cnstr] |
scoped_allocator_adaptor constructors must be constrained |
Yes |
0 |
|
| 3116 |
WP |
19.13.4 [allocator.adaptor.members] |
OUTERMOST_ALLOC_TRAITS needs remove_reference_t |
Yes |
0 |
|
| 2586 |
C++17 |
19.13.4 [allocator.adaptor.members] |
Wrong value category used in scoped_allocator_adaptor::construct() |
Yes |
0 |
|
| 2203 |
C++14 |
19.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor uses wrong argument types for piecewise construction |
Yes |
|
|
| 2511 |
Resolved |
19.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor piecewise construction does not require CopyConstructible |
Yes |
3 |
|
| 1321 |
Resolved |
19.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor construct and destroy don't
use allocator_traits |
Yes |
|
|
| 2717 |
NAD |
19.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor uses forward to do move's job |
Yes |
|
|
| 2048 |
C++14 |
19.14 [function.objects] |
Unnecessary mem_fn overloads |
Yes |
|
|
| 2149 |
C++14 |
19.14 [function.objects] |
Concerns about 20.8/5 |
Yes |
|
|
| 185 |
CD1 |
19.14 [function.objects] |
Questionable use of term "inline" |
Yes |
|
|
| 660 |
CD1 |
19.14 [function.objects] |
Missing Bitwise Operations |
Yes |
|
|
| 1290 |
Resolved |
19.14 [function.objects] |
Don't require [u|bi]nary_function inheritance |
Yes |
|
|
| 658 |
Resolved |
19.14 [function.objects] |
Two unspecified function comparators in [function.objects] |
Yes |
|
|
| 1397 |
Resolved |
19.14 [function.objects] |
Deprecate '98 binders |
Yes |
|
|
| 351 |
NAD Editorial |
19.14 [function.objects] |
unary_negate and binary_negate: struct or class? |
Yes |
|
|
| 1398 |
NAD |
19.14 [function.objects] |
Users should be able to specialize functors without depending on whole <functional> header |
Yes |
|
|
| 2219 |
C++17 |
19.14.3 [func.require] |
INVOKE-ing a pointer to member with a reference_wrapper as the object expression |
Yes |
2 |
|
| 2387 |
C++17 |
19.14.3 [func.require] |
More nested types that must be accessible and unambiguous |
Yes |
|
|
| 2486 |
C++17 |
19.14.3 [func.require] |
mem_fn() should be required to use perfect forwarding |
Yes |
0 |
|
| 1294 |
C++11 |
19.14.3 [func.require] |
Difference between callable wrapper and forwarding call wrapper unclear |
Yes |
|
|
| 1295 |
C++11 |
19.14.3 [func.require] |
Contradictory call wrapper requirements |
Yes |
|
|
| 1520 |
C++11 |
19.14.3 [func.require] |
INVOKE on member data pointer with too many arguments |
Yes |
|
|
| 2926 |
Resolved |
19.14.3 [func.require] |
INVOKE(f, t1, t2,... tN) and INVOKE(f, t1, t2,... tN, R) are too similar |
Yes |
|
|
| 2894 |
Open |
19.14.4 [func.invoke] |
The function template std::apply() is required to be constexpr, but std::invoke() isn't |
Yes |
3 |
|
| 2690 |
LEWG |
19.14.4 [func.invoke] |
invoke<R> |
Yes |
|
|
| 2807 |
C++17 |
19.14.4 [func.invoke] |
std::invoke should use std::is_nothrow_callable |
Yes |
3 |
|
| 3046 |
New |
19.14.5 [refwrap] |
Do not require reference_wrapper to support non-referenceable function types |
Yes |
3 |
|
| 2981 |
WP |
19.14.5 [refwrap] |
Remove redundant deduction guides from standard library |
Yes |
0 |
|
| 2993 |
WP |
19.14.5 [refwrap] |
reference_wrapper<T> conversion from T&& |
Yes |
3 |
|
| 987 |
C++11 |
19.14.5 [refwrap] |
reference_wrapper and function types |
Yes |
|
|
| 2017 |
C++11 |
19.14.5 [refwrap] |
std::reference_wrapper makes incorrect usage of std::result_of |
Yes |
|
|
| 2022 |
C++11 |
19.14.5 [refwrap] |
reference_wrapper<T>::result_type is underspecified |
Yes |
|
|
| 521 |
CD1 |
19.14.5 [refwrap] |
Garbled requirements for argument_type in reference_wrapper |
Yes |
|
|
| 3041 |
WP |
19.14.5.1 [refwrap.const] |
Unnecessary decay in reference_wrapper |
Yes |
0 |
|
| 688 |
C++11 |
19.14.5.1 [refwrap.const] |
reference_wrapper, cref unsafe, allow binding to rvalues |
Yes |
|
|
| 689 |
CD1 |
19.14.5.1 [refwrap.const] |
reference_wrapper constructor overly constrained |
Yes |
|
|
| 2435 |
C++17 |
19.14.5.4 [refwrap.invoke] |
reference_wrapper::operator()'s Remark should be deleted |
Yes |
4 |
|
| 3146 |
New |
19.14.5.5 [refwrap.helpers] |
Excessive unwrapping in std::ref/cref |
Yes |
3 |
|
| 2491 |
New |
19.14.7 [comparisons] |
std::less<T*> in constant expression |
Yes |
3 |
|
| 2547 |
New |
19.14.7 [comparisons] |
Container requirements (and other library text) should say "strict total order", not just "total order" |
No |
3 |
|
| 2450 |
C++17 |
19.14.7 [comparisons] |
(greater|less|greater_equal|less_equal)<void> do not yield a total order for pointers |
Yes |
2 |
|
| 2562 |
C++17 |
19.14.7 [comparisons] |
Consistent total ordering of pointers by comparison functors |
Yes |
3 |
|
| 284 |
CD1 |
19.14.7 [comparisons] |
unportable example in 20.3.7, p6 |
Yes |
|
|
| 297 |
CD1 |
19.14.9 [logical.operations] |
const_mem_fun_t<>::argument_type should be const T* |
Yes |
|
|
| 2767 |
C++17 |
19.14.12 [func.not_fn] |
not_fn call_wrapper can form invalid types |
Yes |
0 |
|
| 520 |
CD1 |
19.14.14 [func.bind] |
Result_of and pointers to data members |
Yes |
|
|
| 2010 |
C++14 |
19.14.14.1 [func.bind.isbind] |
is_* traits for binding operations can't be meaningfully specialized |
Yes |
|
|
| 1071 |
C++11 |
19.14.14.1 [func.bind.isbind] |
is_bind_expression should derive from integral_constant<bool> |
Yes |
|
|
| 2957 |
New |
19.14.14.3 [func.bind.bind] |
bind's specification doesn't apply the cv-qualification of the call wrapper to the callable object |
Yes |
3 |
|
| 2487 |
C++17 |
19.14.14.3 [func.bind.bind] |
bind() should be const-overloaded, not cv-overloaded |
Yes |
2 |
|
| 2545 |
C++17 |
19.14.14.3 [func.bind.bind] |
Simplify wording for bind without explicitly specified return type |
Yes |
3 |
|
| 2021 |
C++14 |
19.14.14.3 [func.bind.bind] |
Further incorrect usages of result_of |
Yes |
|
|
| 817 |
C++11 |
19.14.14.3 [func.bind.bind] |
bind needs to be moved |
Yes |
|
|
| 527 |
CD1 |
19.14.14.3 [func.bind.bind] |
tr1::bind has lost its Throws clause |
Yes |
|
|
| 816 |
Resolved |
19.14.14.3 [func.bind.bind] |
Should bind()'s returned functor have a nofail copy ctor when bind() is nofail? |
Yes |
|
|
| 2488 |
C++17 |
19.14.14.4 [func.bind.place] |
Placeholders should be allowed and encouraged to be constexpr |
Yes |
2 |
|
| 3023 |
New |
19.14.15 [func.memfn] |
Clarify unspecified call wrappers |
Yes |
3 |
|
| 2489 |
C++17 |
19.14.15 [func.memfn] |
mem_fn() should be noexcept |
Yes |
0 |
|
| 920 |
C++11 |
19.14.15 [func.memfn] |
Ref-qualification support in the library |
Yes |
|
1230 |
| 1230 |
Dup |
19.14.15 [func.memfn] |
mem_fn and variadic templates |
Yes |
|
920 |
| 770 |
CD1 |
19.14.16 [func.wrap] |
std::function should use rvalue swap |
Yes |
|
|
| 2233 |
C++17 |
19.14.16.1 [func.wrap.badcall] |
bad_function_call::what() unhelpful |
Yes |
3 |
|
| 2062 |
C++17 |
19.14.16.2 [func.wrap.func] |
Effect contradictions w/o no-throw guarantee of std::function swaps |
Yes |
2 |
|
| 2385 |
C++17 |
19.14.16.2 [func.wrap.func] |
function::assign allocator argument doesn't make sense |
Yes |
2 |
|
| 2393 |
C++17 |
19.14.16.2 [func.wrap.func] |
std::function's Callable definition is broken |
Yes |
2 |
|
| 2401 |
C++17 |
19.14.16.2 [func.wrap.func] |
std::function needs more noexcept |
Yes |
0 |
|
| 2420 |
C++17 |
19.14.16.2 [func.wrap.func] |
function<void(ArgTypes...)> does not discard the return value of the target object |
Yes |
1 |
|
| 1070 |
C++11 |
19.14.16.2 [func.wrap.func] |
Ambiguous move overloads in function |
Yes |
|
|
| 1240 |
C++11 |
19.14.16.2 [func.wrap.func] |
Deleted comparison functions of std::function not needed |
Yes |
|
|
| 1399 |
C++11 |
19.14.16.2 [func.wrap.func] |
function does not need an explicit default constructor |
Yes |
|
|
| 769 |
CD1 |
19.14.16.2 [func.wrap.func] |
std::function should use nullptr_t instead of "unspecified-null-pointer-type" |
Yes |
|
|
| 2370 |
Resolved |
19.14.16.2 [func.wrap.func] |
Operations involving type-erased allocators should not be noexcept in std::function |
Yes |
3 |
|
| 2501 |
Resolved |
19.14.16.2 [func.wrap.func] |
std::function requires POCMA/POCCA |
Yes |
3 |
|
| 2502 |
Resolved |
19.14.16.2 [func.wrap.func] |
std::function does not use allocator::construct |
Yes |
3 |
|
| 1023 |
NAD Editorial |
19.14.16.2 [func.wrap.func] |
Unclear inheritance relation for std::function |
Yes |
|
|
| 644 |
NAD |
19.14.16.2 [func.wrap.func] |
Possible typos in 'function' description |
Yes |
|
|
| 1024 |
NAD Concepts |
19.14.16.2 [func.wrap.func] |
std::function constructors overly generous |
Yes |
|
|
| 1059 |
NAD Concepts |
19.14.16.2 [func.wrap.func] |
Usage of no longer existing FunctionType concept |
Yes |
|
|
| 2774 |
New |
19.14.16.2.1 [func.wrap.func.con] |
std::function construction vs assignment |
No |
3 |
|
| 2813 |
EWG |
19.14.16.2.1 [func.wrap.func.con] |
std::function should not return dangling references |
Yes |
2 |
|
| 2565 |
C++17 |
19.14.16.2.1 [func.wrap.func.con] |
std::function's move constructor should guarantee nothrow for reference_wrappers and function pointers |
Yes |
0 |
|
| 2781 |
C++17 |
19.14.16.2.1 [func.wrap.func.con] |
Contradictory requirements for std::function and std::reference_wrapper |
Yes |
0 |
|
| 2850 |
C++17 |
19.14.16.2.1 [func.wrap.func.con] |
std::function move constructor does unnecessary work |
Yes |
0 |
|
| 2132 |
C++14 |
19.14.16.2.1 [func.wrap.func.con] |
std::function ambiguity |
Yes |
2 |
|
| 1287 |
C++11 |
19.14.16.2.1 [func.wrap.func.con] |
std::function requires CopyConstructible target object |
Yes |
|
|
| 1288 |
C++11 |
19.14.16.2.1 [func.wrap.func.con] |
std::function assignment from rvalues |
Yes |
|
|
| 1292 |
C++11 |
19.14.16.2.1 [func.wrap.func.con] |
std::function should support all callable types |
Yes |
|
|
| 1400 |
C++11 |
19.14.16.2.1 [func.wrap.func.con] |
FCD function does not need an explicit default constructor |
Yes |
|
|
| 610 |
CD1 |
19.14.16.2.1 [func.wrap.func.con] |
Suggested non-normative note for C++0x |
Yes |
|
|
| 2386 |
NAD |
19.14.16.2.1 [func.wrap.func.con] |
function::operator= handles allocators incorrectly |
Yes |
1 |
|
| 1258 |
Resolved |
19.14.16.2.2 [func.wrap.func.mod] |
std::function Effects clause impossible to satisfy |
Yes |
|
|
| 1333 |
C++11 |
19.14.16.2.4 [func.wrap.func.inv] |
Missing forwarding during std::function invocation |
Yes |
|
|
| 815 |
Resolved |
19.14.16.2.4 [func.wrap.func.inv] |
std::function and reference_closure do not use perfect forwarding |
Yes |
|
|
| 2591 |
C++17 |
19.14.16.2.5 [func.wrap.func.targ] |
std::function's member template target() should not lead to undefined behaviour |
Yes |
3 |
|
| 633 |
NAD Editorial |
19.14.16.2.5 [func.wrap.func.targ] |
Return clause mentions undefined "type()" |
Yes |
|
|
| 1317 |
Tentatively NAD |
19.14.18 [unord.hash] |
make_hash |
Yes |
|
|
| 1025 |
LEWG |
19.14.18 [unord.hash] |
The library should provide more specializations for std::hash |
No |
|
|
| 2119 |
C++17 |
19.14.18 [unord.hash] |
Missing hash specializations for extended integer types |
Yes |
3 |
|
| 2148 |
C++14 |
19.14.18 [unord.hash] |
Hashing enums should be supported directly by std::hash |
Yes |
|
|
| 978 |
C++11 |
19.14.18 [unord.hash] |
Hashing smart pointers |
Yes |
|
|
| 1182 |
C++11 |
19.14.18 [unord.hash] |
Unfortunate hash dependencies |
Yes |
|
|
| 1245 |
C++11 |
19.14.18 [unord.hash] |
std::hash<string> & co |
Yes |
|
|
| 848 |
CD1 |
19.14.18 [unord.hash] |
Missing std::hash specializations for std::bitset/std::vector<bool> |
Yes |
|
|
| 2803 |
Resolved |
19.14.18 [unord.hash] |
hash for arithmetic, pointer and standard library types should not throw |
Yes |
3 |
|
| 2543 |
Resolved |
19.14.18 [unord.hash] |
LWG 2148 (hash support for enum types) seems under-specified |
Yes |
2 |
|
| 2817 |
Resolved |
19.14.18 [unord.hash] |
std::hash for nullptr_t |
Yes |
|
|
| 1072 |
NAD Concepts |
19.14.18 [unord.hash] |
Is std::hash a constrained template or not? |
Yes |
|
|
| 2290 |
Open |
19.15 [meta] |
Top-level "SFINAE"-based constraints should get a separate definition in Clause 17 |
Yes |
3 |
|
| 2452 |
Core |
19.15 [meta] |
is_constructible, etc. and default arguments |
No |
3 |
|
| 2582 |
C++17 |
19.15 [meta] |
§[res.on.functions]/2's prohibition against incomplete types shouldn't apply to type traits |
Yes |
0 |
|
| 1114 |
C++11 |
19.15 [meta] |
Type traits underspecified |
Yes |
|
|
| 2040 |
Resolved |
19.15 [meta] |
Missing type traits related to is_convertible |
Yes |
|
|
| 719 |
Resolved |
19.15 [meta] |
std::is_literal type traits should be provided |
Yes |
|
750 |
| 1390 |
Resolved |
19.15 [meta] |
Limit speculative compilation for constructible/convertible traits |
Yes |
|
|
| 1391 |
Resolved |
19.15 [meta] |
constructible/convertible traits and access control |
Yes |
|
|
| 590 |
NAD Editorial |
19.15 [meta] |
Type traits implementation latitude should be removed for C++0x |
Yes |
|
|
| 1120 |
NAD |
19.15 [meta] |
New type trait - remove_all |
Yes |
|
|
| 1018 |
NAD Concepts |
19.15 [meta] |
Trait specifications should be expressed in terms of concepts |
Yes |
|
|
| 2845 |
New |
19.15.1 [meta.rqmts] |
enable_if, result_of, common_type and aligned_storage do not meet the definition
of TransformationTrait |
No |
3 |
|
| 2514 |
C++17 |
19.15.1 [meta.rqmts] |
Type traits must not be final |
Yes |
3 |
|
| 2939 |
New |
19.15.2 [meta.type.synop] |
Some type-completeness constraints of traits are overspecified |
No |
2 |
|
| 3099 |
New |
19.15.2 [meta.type.synop] |
is_assignable<Incomplete&, Incomplete&> |
Yes |
|
|
| 2922 |
LEWG |
19.15.2 [meta.type.synop] |
The *_constant<> templates do not make use of template<auto> |
No |
|
|
| 2581 |
C++17 |
19.15.2 [meta.type.synop] |
Specialization of <type_traits> variable templates should be prohibited |
Yes |
0 |
|
| 2797 |
Resolved |
19.15.2 [meta.type.synop] |
Trait precondition violations |
Yes |
2 |
|
| 2927 |
Resolved |
19.15.2 [meta.type.synop] |
Encoding a functor and argument types as a function signature for is_callable and result_of is fragile |
Yes |
|
|
| 2928 |
Resolved |
19.15.2 [meta.type.synop] |
is_callable is not a good name |
Yes |
|
|
| 2871 |
NAD |
19.15.2 [meta.type.synop] |
User specializations of type traits should be ill-formed |
Yes |
|
|
| 2910 |
Dup |
19.15.2 [meta.type.synop] |
Template deduction and integral_constant |
Yes |
|
|
| 2346 |
C++14 |
19.15.3 [meta.help] |
integral_constant's member functions should be marked noexcept |
Yes |
0 |
|
| 1019 |
C++11 |
19.15.3 [meta.help] |
Make integral_constant objects useable in integral-constant-expressions |
Yes |
|
|
| 1202 |
NAD |
19.15.3 [meta.help] |
integral_constant needs a spring clean |
Yes |
|
|
| 1092 |
NAD Concepts |
19.15.3 [meta.help] |
Class template integral_constant should be a constrained template |
Yes |
|
|
| 2015 |
C++14 |
19.15.4 [meta.unary] |
Incorrect pre-conditions for some type traits |
Yes |
|
|
| 525 |
Resolved |
19.15.4 [meta.unary] |
type traits definitions not clear |
Yes |
|
|
| 1392 |
Resolved |
19.15.4 [meta.unary] |
result_of should support pointer-to-data-member |
Yes |
|
|
| 2247 |
C++14 |
19.15.4.1 [meta.unary.cat] |
Type traits and std::nullptr_t |
Yes |
|
|
| 2496 |
New |
19.15.4.3 [meta.unary.prop] |
Certain hard-to-avoid errors not in the immediate context are not allowed to be triggered by
the evaluation of type traits |
No |
3 |
|
| 2827 |
New |
19.15.4.3 [meta.unary.prop] |
is_trivially_constructible and non-trivial destructors |
No |
3 |
|
| 2116 |
Open |
19.15.4.3 [meta.unary.prop] |
is_nothrow_constructible and destructors |
No |
3 |
|
| 2077 |
Open |
19.15.4.3 [meta.unary.prop] |
Further incomplete constraints for type traits |
No |
3 |
|
| 2358 |
Open |
19.15.4.3 [meta.unary.prop] |
Apparently-bogus definition of is_empty type trait |
Yes |
3 |
|
| 2972 |
WP |
19.15.4.3 [meta.unary.prop] |
What is is_trivially_destructible_v<int>? |
Yes |
|
|
| 2336 |
C++17 |
19.15.4.3 [meta.unary.prop] |
is_trivially_constructible/is_trivially_assignable traits are always false |
Yes |
3 |
|
| 2367 |
C++17 |
19.15.4.3 [meta.unary.prop] |
pair and tuple are not correctly implemented for is_constructible with no args |
Yes |
3 |
|
| 2560 |
C++17 |
19.15.4.3 [meta.unary.prop] |
is_constructible underspecified when applied to a function type |
Yes |
0 |
|
| 2738 |
C++17 |
19.15.4.3 [meta.unary.prop] |
is_constructible with void types |
Yes |
|
|
| 2911 |
C++17 |
19.15.4.3 [meta.unary.prop] |
An is_aggregate type trait is needed |
Yes |
|
|
| 2049 |
C++14 |
19.15.4.3 [meta.unary.prop] |
is_destructible is underspecified |
Yes |
|
|
| 2196 |
C++14 |
19.15.4.3 [meta.unary.prop] |
Specification of is_*[copy/move]_[constructible/assignable] unclear for non-referencable types |
Yes |
|
|
| 2197 |
C++14 |
19.15.4.3 [meta.unary.prop] |
Specification of is_[un]signed unclear for non-arithmetic types |
Yes |
|
|
| 2298 |
C++14 |
19.15.4.3 [meta.unary.prop] |
[CD] is_nothrow_constructible is always false because of create<> |
Yes |
|
|
| 931 |
C++11 |
19.15.4.3 [meta.unary.prop] |
type trait extent<T, I> |
Yes |
|
|
| 1131 |
C++11 |
19.15.4.3 [meta.unary.prop] |
C++0x does not need alignment_of |
Yes |
|
|
| 749 |
CD1 |
19.15.4.3 [meta.unary.prop] |
Currently has_nothrow_copy_constructor<T>::value is true if T has 'a' nothrow copy constructor. |
Yes |
|
|
| 1174 |
Resolved |
19.15.4.3 [meta.unary.prop] |
Type property predicates |
Yes |
|
|
| 1260 |
Resolved |
19.15.4.3 [meta.unary.prop] |
is_constructible<int*,void*> reports true |
Yes |
|
|
| 1393 |
Resolved |
19.15.4.3 [meta.unary.prop] |
Trivial traits imply noexcept |
Yes |
|
|
| 1394 |
Resolved |
19.15.4.3 [meta.unary.prop] |
is_constructible reports false positives |
Yes |
|
|
| 1239 |
NAD Editorial |
19.15.4.3 [meta.unary.prop] |
Defect report |
Yes |
|
|
| 2828 |
NAD Editorial |
19.15.4.3 [meta.unary.prop] |
Clarify <cstdalign> (following adoption of P0063r3) |
Yes |
|
|
| 747 |
NAD |
19.15.4.3 [meta.unary.prop] |
We have 3 separate type traits to identify classes supporting no-throw operations |
Yes |
|
|
| 748 |
NAD |
19.15.4.3 [meta.unary.prop] |
The is_abstract type trait is defined by reference to 10.4. |
Yes |
|
|
| 1228 |
NAD |
19.15.4.3 [meta.unary.prop] |
User-specialized nothrow type traits |
Yes |
|
|
| 2317 |
C++14 |
19.15.5 [meta.unary.prop.query] |
The type property queries should be UnaryTypeTraits returning size_t |
Yes |
0 |
|
| 975 |
C++11 |
19.15.6 [meta.rel] |
is_convertible cannot be instantiated for non-convertible types |
Yes |
|
|
| 3022 |
Resolved |
19.15.6 [meta.rel] |
is_convertible<derived*, base*> may lead to ODR |
Yes |
2 |
|
| 2895 |
Resolved |
19.15.6 [meta.rel] |
Passing function types to result_of and is_callable |
Yes |
|
|
| 1395 |
NAD Editorial |
19.15.6 [meta.rel] |
Inconsistent reference links should be unified |
Yes |
|
|
| 750 |
Dup |
19.15.6 [meta.rel] |
The current definition for is_convertible requires that the type be
implicitly convertible, so explicit constructors are ignored. |
Yes |
|
719 |
| 2101 |
C++17 |
19.15.7 [meta.trans] |
Some transformation types can produce impossible types |
Yes |
3 |
|
| 3152 |
New |
19.15.7.6 [meta.trans.other] |
common_type and common_reference have flaws in common |
Yes |
3 |
|
| 3140 |
WP |
19.15.7.6 [meta.trans.other] |
COMMON_REF is unimplementable as specified |
Yes |
0 |
|
| 3034 |
WP |
19.15.7.6 [meta.trans.other] |
P0767R1 breaks previously-standard-layout types |
Yes |
0 |
|
| 2979 |
WP |
19.15.7.6 [meta.trans.other] |
aligned_union should require complete object types |
Yes |
0 |
|
| 2396 |
C++17 |
19.15.7.6 [meta.trans.other] |
underlying_type doesn't say what to do for an incomplete enumeration type |
Yes |
0 |
|
| 2408 |
C++17 |
19.15.7.6 [meta.trans.other] |
SFINAE-friendly common_type/iterator_traits is missing in C++14 |
Yes |
|
|
| 2460 |
C++17 |
19.15.7.6 [meta.trans.other] |
LWG issue 2408 and value categories |
Yes |
2 |
|
| 2141 |
C++14 |
19.15.7.6 [meta.trans.other] |
common_type trait produces reference types |
Yes |
|
|
| 1187 |
C++11 |
19.15.7.6 [meta.trans.other] |
std::decay |
Yes |
|
|
| 705 |
CD1 |
19.15.7.6 [meta.trans.other] |
type-trait decay incompletely specified |
Yes |
|
|
| 856 |
CD1 |
19.15.7.6 [meta.trans.other] |
Removal of aligned_union |
Yes |
|
|
| 2465 |
Resolved |
19.15.7.6 [meta.trans.other] |
SFINAE-friendly common_type is nearly impossible to specialize
correctly and regresses key functionality |
Yes |
2 |
|
| 1055 |
Resolved |
19.15.7.6 [meta.trans.other] |
Provide a trait that returns the underlying type of an enumeration type |
Yes |
|
|
| 2397 |
Resolved |
19.15.7.6 [meta.trans.other] |
map<K, V>::emplace and explicit V constructors |
Yes |
1 |
|
| 2763 |
Resolved |
19.15.7.6 [meta.trans.other] |
common_type_t<void, void> is undefined |
Yes |
2 |
|
| 849 |
NAD |
19.15.7.6 [meta.trans.other] |
missing type traits to compute root class and derived class of types in a class hierachy |
Yes |
|
|
| 1020 |
NAD |
19.15.7.6 [meta.trans.other] |
Restore aligned_union |
Yes |
|
|
| 2569 |
C++17 |
19.15.8 [meta.logical] |
conjunction and disjunction requirements are too strict |
Yes |
2 |
|
| 2587 |
C++17 |
19.15.8 [meta.logical] |
"Convertible to bool" requirement in conjunction and disjunction |
Yes |
3 |
|
| 2557 |
C++17 |
19.15.8 [meta.logical] |
Logical operator traits are broken in the zero-argument case |
Yes |
0 |
|
| 2567 |
C++17 |
19.15.8 [meta.logical] |
Specification of logical operator traits uses BaseCharacteristic, which is defined only for UnaryTypeTraits
and BinaryTypeTraits |
Yes |
2 |
|
| 921 |
C++11 |
19.16.3 [ratio.ratio] |
Rational Arithmetic should use template aliases |
Yes |
|
|
| 1388 |
C++11 |
19.16.3 [ratio.ratio] |
LWG 1281 incorrectly accepted |
Yes |
|
|
| 1122 |
Resolved |
19.16.3 [ratio.ratio] |
Ratio values should be constexpr |
Yes |
|
|
| 1281 |
Resolved |
19.16.3 [ratio.ratio] |
CopyConstruction and Assignment between ratios having the same normalized form |
Yes |
|
|
| 1121 |
Tentatively NAD |
19.16.4 [ratio.arithmetic] |
Support for multiple arguments |
Yes |
|
|
| 948 |
C++11 |
19.16.4 [ratio.arithmetic] |
ratio arithmetic tweak |
Yes |
|
|
| 1389 |
Resolved |
19.16.4 [ratio.arithmetic] |
Compile-time rational arithmetic and overflow |
Yes |
|
|
| 2144 |
C++14 |
19.17 [type.index] |
Missing noexcept specification in type_index |
Yes |
|
|
| 1078 |
NAD Concepts |
19.17 [type.index] |
DE-17: Remove class type_index |
Yes |
|
|
| 2909 |
NAD |
19.18.3 [execpol.type] |
User specializations of is_execution_policy should be ill-formed |
Yes |
|
|
| 3081 |
Open |
19.19.3 [charconv.from.chars] |
Floating point from_chars API does not distinguish between overflow and underflow |
Yes |
2 |
|
| 3082 |
Open |
19.19.3 [charconv.from.chars] |
from_chars specification regarding floating point rounding is inconsistent |
Yes |
2 |
|
| 3080 |
WP |
19.19.3 [charconv.from.chars] |
Floating point from_chars pattern specification breaks round-tripping |
Yes |
0 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 7 |
TC1 |
20 [strings] |
String clause minor problems |
Yes |
|
|
| 2841 |
Resolved |
20 [strings] |
Use of "Equivalent to" in [strings] |
Yes |
3 |
|
| 85 |
NAD |
20 [strings] |
String char types |
Yes |
|
|
| 1081 |
NAD Concepts |
20 [strings] |
basic_string needs to be a concept-constrained template |
Yes |
|
|
| 2513 |
New |
20.1 [strings.general] |
Missing requirements for basic_string::value_type |
No |
4 |
|
| 1170 |
C++11 |
20.1 [strings.general] |
String char-like types no longer PODs |
Yes |
|
|
| 2994 |
Open |
20.2 [char.traits] |
Needless UB for basic_string and basic_string_view |
Yes |
3 |
|
| 830 |
NAD Editorial |
20.2 [char.traits] |
Incomplete list of char_traits specializations |
Yes |
|
|
| 570 |
NAD |
20.2 [char.traits] |
Request adding additional explicit specializations of char_traits |
Yes |
|
|
| 3085 |
Open |
20.2.1 [char.traits.require] |
char_traits::copy precondition too weak |
Yes |
2 |
|
| 335 |
CD1 |
20.2.1 [char.traits.require] |
minor issue with char_traits, table 37 |
Yes |
|
|
| 352 |
CD1 |
20.2.2 [char.traits.typedefs] |
missing fpos requirements |
Yes |
|
|
| 1200 |
NAD |
20.2.2 [char.traits.typedefs] |
"surprising" char_traits<T>::int_type requirements |
Yes |
|
|
| 709 |
CD1 |
20.2.3 [char.traits.specializations] |
char_traits::not_eof has wrong signature |
Yes |
|
|
| 2232 |
Resolved |
20.2.3 [char.traits.specializations] |
[CD] The char_traits specializations should declare their length(), compare(), and
find() members constexpr |
Yes |
|
|
| 831 |
NAD Editorial |
20.2.3 [char.traits.specializations] |
wrong type for not_eof() |
Yes |
|
|
| 467 |
CD1 |
20.2.3.1 [char.traits.specializations.char] |
char_traits::lt(), compare(), and memcmp() |
Yes |
|
|
| 2959 |
New |
20.2.3.3 [char.traits.specializations.char16_t] |
char_traits<char16_t>::eof is a valid UTF-16 code unit |
No |
3 |
|
| 1414 |
C++11 |
20.2.3.3 [char.traits.specializations.char16_t] |
Fixing remaining dead links to POS_T and OFF_T |
Yes |
|
1444 |
| 57 |
TC1 |
20.2.3.5 [char.traits.specializations.wchar.t] |
Mistake in char_traits |
Yes |
|
|
| 3165 |
LEWG |
20.3.2 [basic.string] |
All starts_with() overloads should be called "begins_with" |
Yes |
2 |
|
| 3075 |
WP |
20.3.2 [basic.string] |
basic_string needs deduction guides from basic_string_view |
Yes |
|
|
| 2063 |
C++17 |
20.3.2 [basic.string] |
Contradictory requirements for string move assignment |
Yes |
3 |
|
| 2064 |
C++14 |
20.3.2 [basic.string] |
More noexcept issues in basic_string |
Yes |
|
|
| 2268 |
C++14 |
20.3.2 [basic.string] |
Setting a default argument in the declaration of a member function assign of std::basic_string |
Yes |
|
|
| 876 |
C++11 |
20.3.2 [basic.string] |
basic_string access operations should give stronger guarantees |
Yes |
|
|
| 180 |
CD1 |
20.3.2 [basic.string] |
Container member iterator arguments constness has unintended consequences |
Yes |
|
|
| 263 |
CD1 |
20.3.2 [basic.string] |
Severe restriction on basic_string reference counting |
Yes |
|
|
| 530 |
CD1 |
20.3.2 [basic.string] |
Must elements of a string be contiguous? |
Yes |
|
|
| 534 |
CD1 |
20.3.2 [basic.string] |
Missing basic_string members |
Yes |
|
|
| 42 |
TC1 |
20.3.2 [basic.string] |
String ctors specify wrong default allocator |
Yes |
|
|
| 83 |
TC1 |
20.3.2 [basic.string] |
String::npos vs. string::max_size() |
Yes |
|
89 |
| 209 |
TC1 |
20.3.2 [basic.string] |
basic_string declarations inconsistent |
Yes |
|
|
| 2318 |
Resolved |
20.3.2 [basic.string] |
basic_string's wording has confusing relics from the copy-on-write era |
Yes |
4 |
|
| 2836 |
Resolved |
20.3.2 [basic.string] |
More string operations should be noexcept |
Yes |
2 |
|
| 2391 |
Resolved |
20.3.2 [basic.string] |
basic_string is missing non-const data() |
Yes |
3 |
|
| 718 |
NAD Editorial |
20.3.2 [basic.string] |
basic_string is not a sequence |
Yes |
|
|
| 2372 |
NAD |
20.3.2 [basic.string] |
Assignment from int to std::string |
Yes |
4 |
|
| 4 |
NAD |
20.3.2 [basic.string] |
basic_string size_type and difference_type should be implementation defined |
Yes |
|
|
| 614 |
NAD |
20.3.2 [basic.string] |
std::string allocator requirements still inconsistent |
Yes |
|
|
| 2084 |
NAD |
20.3.2 [basic.string] |
basic_string use of charT* |
Yes |
|
|
| 2760 |
C++17 |
20.3.2.1 [string.require] |
non-const basic_string::data should not invalidate iterators |
Yes |
|
|
| 2861 |
C++17 |
20.3.2.1 [string.require] |
basic_string should require that charT match traits::char_type |
Yes |
|
|
| 2003 |
C++14 |
20.3.2.1 [string.require] |
String exception inconsistency in erase. |
Yes |
0 |
|
| 847 |
C++11 |
20.3.2.1 [string.require] |
string exception safety guarantees |
Yes |
|
|
| 301 |
CD1 |
20.3.2.1 [string.require] |
basic_string template ctor effects clause omits allocator argument |
Yes |
|
|
| 86 |
TC1 |
20.3.2.1 [string.require] |
String constructors don't describe exceptions |
Yes |
|
|
| 2151 |
Resolved |
20.3.2.1 [string.require] |
basic_string<>::swap semantics ignore allocators |
Yes |
3 |
|
| 466 |
NAD |
20.3.2.1 [string.require] |
basic_string ctor should prevent null pointer error |
Yes |
|
|
| 3076 |
WP |
20.3.2.2 [string.cons] |
basic_string CTAD ambiguity |
Yes |
|
|
| 2946 |
WP |
20.3.2.2 [string.cons] |
LWG 2758's resolution missed further corrections |
Yes |
2 |
|
| 2583 |
C++17 |
20.3.2.2 [string.cons] |
There is no way to supply an allocator for basic_string(str, pos) |
Yes |
0 |
|
| 2742 |
C++17 |
20.3.2.2 [string.cons] |
Inconsistent string interface taking string_view |
Yes |
1 |
|
| 2069 |
C++14 |
20.3.2.2 [string.cons] |
Inconsistent exception spec for basic_string move constructor |
Yes |
|
|
| 2235 |
C++14 |
20.3.2.2 [string.cons] |
Undefined behavior without proper requirements on basic_string constructors |
Yes |
|
|
| 3111 |
Resolved |
20.3.2.2 [string.cons] |
Too strong precondition on basic_string constructor |
Yes |
2 |
|
| 3033 |
NAD Editorial |
20.3.2.2 [string.cons] |
basic_string move ctor is underspecified |
Yes |
|
|
| 2319 |
NAD |
20.3.2.2 [string.cons] |
basic_string's move constructor should not be noexcept |
Yes |
1 |
|
| 2402 |
NAD |
20.3.2.2 [string.cons] |
basic_string(const basic_string& str, size_type pos, size_type n = npos) shouldn't use Allocator() |
Yes |
3 |
|
| 2580 |
NAD |
20.3.2.2 [string.cons] |
Who is definitive: operator= or assign? |
Yes |
4 |
|
| 2822 |
NAD |
20.3.2.2 [string.cons] |
Resolution for LWG 2742 introduces ambiguities |
Yes |
|
|
| 1192 |
C++11 |
20.3.2.3 [string.iterators] |
basic_string missing definitions for cbegin / cend / crbegin / crend |
Yes |
|
|
| 3004 |
WP |
20.3.2.4 [string.capacity] |
§[string.capacity] and §[vector.capacity] should specify time complexity for capacity() |
Yes |
0 |
|
| 2834 |
C++17 |
20.3.2.4 [string.capacity] |
Resolution LWG 2223 is missing wording about end iterators |
Yes |
0 |
|
| 259 |
CD1 |
20.3.2.4 [string.capacity] |
basic_string::operator[] and const correctness |
Yes |
|
|
| 2968 |
Resolved |
20.3.2.4 [string.capacity] |
Inconsistencies between basic_string reserve and vector/unordered_map/unordered_set reserve functions |
Yes |
3 |
|
| 104 |
NAD |
20.3.2.4 [string.capacity] |
Description of basic_string::operator[] is unclear |
Yes |
|
|
| 2475 |
C++17 |
20.3.2.5 [string.access] |
Allow overwriting of std::basic_string terminator with charT() to allow
cleaner interoperation with legacy APIs |
Yes |
3 |
|
| 2207 |
C++14 |
20.3.2.5 [string.access] |
basic_string::at should not have a Requires clause |
Yes |
|
|
| 84 |
NAD |
20.3.2.5 [string.access] |
Ambiguity with string::insert() |
Yes |
|
|
| 2788 |
C++17 |
20.3.2.6.2 [string.append] |
basic_string range mutators unintentionally require a default constructible allocator |
Yes |
2 |
|
| 2579 |
C++17 |
20.3.2.6.3 [string.assign] |
Inconsistency wrt Allocators in basic_string assignment vs. basic_string::assign |
Yes |
0 |
|
| 2758 |
C++17 |
20.3.2.6.3 [string.assign] |
std::string{}.assign("ABCDE", 0, 1) is ambiguous |
Yes |
1 |
|
| 2929 |
Resolved |
20.3.2.6.3 [string.assign] |
basic_string misuses "Effects: Equivalent to" |
Yes |
3 |
|
| 141 |
TC1 |
20.3.2.6.4 [string.insert] |
basic_string::find_last_of, find_last_not_of say pos instead of xpos |
Yes |
|
|
| 2757 |
Resolved |
20.3.2.6.4 [string.insert] |
std::string{}.insert(3, "ABCDE", 0, 1) is ambiguous |
Yes |
1 |
|
| 88 |
NAD |
20.3.2.6.4 [string.insert] |
Inconsistency between string::insert() and string::append() |
Yes |
|
|
| 377 |
NAD |
20.3.2.6.4 [string.insert] |
basic_string::insert and length_error |
Yes |
|
|
| 89 |
Dup |
20.3.2.6.4 [string.insert] |
Missing throw specification for string::insert() and string::replace() |
Yes |
|
83 |
| 428 |
CD1 |
20.3.2.6.5 [string.erase] |
string::erase(iterator) validity |
Yes |
|
|
| 27 |
TC1 |
20.3.2.6.5 [string.erase] |
String::erase(range) yields wrong iterator |
Yes |
|
|
| 1323 |
C++11 |
20.3.2.6.6 [string.replace] |
basic_string::replace should use const_iterator |
Yes |
|
|
| 368 |
NAD Editorial |
20.3.2.6.6 [string.replace] |
basic_string::replace has two "Throws" paragraphs |
Yes |
|
|
| 403 |
CD1 |
20.3.2.6.8 [string.swap] |
basic_string::swap should not throw exceptions |
Yes |
|
|
| 535 |
CD1 |
20.3.2.6.8 [string.swap] |
std::string::swap specification poorly worded |
Yes |
|
|
| 5 |
TC1 |
20.3.2.6.8 [string.swap] |
String::compare specification questionable |
Yes |
|
87 |
| 87 |
Dup |
20.3.2.6.8 [string.swap] |
Error in description of string::compare() |
Yes |
|
5 |
| 2771 |
C++17 |
20.3.2.7.4 [string.compare] |
Broken Effects of some basic_string::compare functions in terms of basic_string_view |
Yes |
1 |
|
| 2011 |
C++14 |
20.3.3.4 [string.io] |
Unexpected output required of strings |
Yes |
|
|
| 91 |
CD1 |
20.3.3.4 [string.io] |
Description of operator>> and getline() for string<> might cause endless loop |
Yes |
|
|
| 435 |
CD1 |
20.3.3.4 [string.io] |
bug in DR 25 |
Yes |
|
|
| 586 |
CD1 |
20.3.3.4 [string.io] |
string inserter not a formatted function |
Yes |
|
|
| 824 |
CD1 |
20.3.3.4 [string.io] |
rvalue ref issue with basic_string inserter |
Yes |
|
|
| 25 |
TC1 |
20.3.3.4 [string.io] |
String operator<< uses width() value wrong |
Yes |
|
67 |
| 90 |
TC1 |
20.3.3.4 [string.io] |
Incorrect description of operator >> for strings |
Yes |
|
|
| 211 |
TC1 |
20.3.3.4 [string.io] |
operator>>(istream&, string&) doesn't set failbit |
Yes |
|
|
| 2535 |
NAD |
20.3.3.4 [string.io] |
Inconsistency between ostream::write and ostream::operator<< |
Yes |
2 |
|
| 67 |
Dup |
20.3.3.4 [string.io] |
Setw useless for strings |
Yes |
|
25 |
| 2403 |
C++17 |
20.3.4 [string.conversions] |
stof() should call strtof() and wcstof() |
Yes |
2 |
|
| 2009 |
C++14 |
20.3.4 [string.conversions] |
Reporting out-of-bound values on numeric string conversions |
Yes |
|
|
| 1261 |
C++11 |
20.3.4 [string.conversions] |
Insufficent overloads for to_string / to_wstring |
Yes |
|
|
| 771 |
CD1 |
20.3.4 [string.conversions] |
Impossible throws clause in [string.conversions] |
Yes |
|
|
| 772 |
CD1 |
20.3.4 [string.conversions] |
Impossible return clause in [string.conversions] |
Yes |
|
|
| 2270 |
NAD |
20.3.4 [string.conversions] |
Inconsistent to_string overloads |
Yes |
|
|
| 2978 |
WP |
20.3.5 [basic.string.hash] |
Hash support for pmr::string and friends |
Yes |
0 |
|
| 2355 |
NAD |
20.3.6 [basic.string.literals] |
"s" UDL suffix should be reserved for a compile-time string library type |
Yes |
1 |
|
| 2883 |
LEWG |
20.4 [string.view] |
The standard library should provide string_view parameters instead or in addition for functions
defined with char const * or string const & as parameter types. |
No |
|
|
| 2778 |
C++17 |
20.4 [string.view] |
basic_string_view is missing constexpr |
Yes |
0 |
|
| 2780 |
Resolved |
20.4 [string.view] |
basic_string_view::copy is missing constexpr |
Yes |
2 |
|
| 3068 |
LEWG |
20.4.2 [string.view.template] |
Forbid assigning an rvalue basic_string to basic_string_view |
Yes |
2 |
|
| 2938 |
Resolved |
20.4.2 [string.view.template] |
basic_string_view::const_iterator should be literal types |
Yes |
2 |
|
| 2826 |
C++17 |
20.4.2.2 [string.view.iterators] |
string_view iterators use old wording |
Yes |
0 |
|
| 3040 |
Tentatively Ready |
20.4.2.6 [string.view.ops] |
basic_string_view::starts_with Effects are incorrect |
Yes |
0 |
|
| 2777 |
C++17 |
20.4.2.6 [string.view.ops] |
basic_string_view::copy should use char_traits::copy |
Yes |
0 |
|
| 2755 |
C++17 |
20.4.4 [string.view.io] |
§[string.view.io] uses non-existent basic_string_view::to_string function |
Yes |
0 |
|
| 2791 |
Resolved |
20.4.5 [string.view.hash] |
string_view objects and strings should yield the same hash values |
Yes |
|
|
| 2237 |
New |
20.5 [c.strings] |
<cuchar> macros |
No |
4 |
|
| 2238 |
Open |
20.5 [c.strings] |
Problematic iterator-pair constructor of containers |
No |
3 |
|
| 2482 |
C++17 |
20.5 [c.strings] |
§[c.strings] Table 73 mentions nonexistent functions |
Yes |
|
|
| 345 |
CD1 |
20.5 [c.strings] |
type tm in <cwchar> |
Yes |
|
|
| 615 |
NAD Editorial |
20.5 [c.strings] |
Inconsistencies in Section 21.4 |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 2307 |
LEWG |
21 [containers] |
Should the Standard Library use explicit only when necessary? |
No |
2 |
|
| 2884 |
LEWG |
21 [containers] |
Relational operators for containers should sfinae; if the underlying type is not comparable, neither should the container be |
No |
|
|
| 2885 |
LEWG |
21 [containers] |
The relational operators of optional and variant completely reflect the semantics of the element
types — this is inconsistent with other types in the library |
No |
|
|
| 2193 |
C++14 |
21 [containers] |
Default constructors for standard library containers are explicit |
Yes |
1 |
|
| 774 |
C++11 |
21 [containers] |
Member swap undefined for most containers |
Yes |
|
|
| 868 |
C++11 |
21 [containers] |
Default construction and value-initialization |
Yes |
|
|
| 883 |
C++11 |
21 [containers] |
swap circular definition |
Yes |
|
|
| 2913 |
Resolved |
21 [containers] |
Containers need deduction guides |
Yes |
|
|
| 767 |
Resolved |
21 [containers] |
Forwarding and backward compatibility |
Yes |
|
|
| 1242 |
NAD |
21 [containers] |
Enable SCARY iterators |
Yes |
|
|
| 97 |
NAD |
21 [containers] |
Insert inconsistent definition |
Yes |
|
|
| 470 |
NAD |
21 [containers] |
accessing containers from their elements' special functions |
Yes |
|
|
| 3059 |
New |
21.2 [container.requirements] |
Wrong requirements for map-like associative container assignment? |
No |
3 |
|
| 2261 |
C++17 |
21.2 [container.requirements] |
Are containers required to use their 'pointer' type internally? |
Yes |
2 |
|
| 704 |
C++11 |
21.2 [container.requirements] |
MoveAssignable requirement for container value type overly strict |
Yes |
|
|
| 861 |
C++11 |
21.2 [container.requirements] |
Incomplete specification of EqualityComparable for std::forward_list |
Yes |
|
|
| 1416 |
C++11 |
21.2 [container.requirements] |
forward_list::erase_after should not be allowed to throw |
Yes |
|
|
| 179 |
CD1 |
21.2 [container.requirements] |
Comparison of const_iterators to iterators doesn't work |
Yes |
|
|
| 276 |
CD1 |
21.2 [container.requirements] |
Assignable requirement for container value type overly strict |
Yes |
|
|
| 322 |
CD1 |
21.2 [container.requirements] |
iterator and const_iterator should have the same value type |
Yes |
|
|
| 371 |
CD1 |
21.2 [container.requirements] |
Stability of multiset and multimap member functions |
Yes |
|
|
| 589 |
CD1 |
21.2 [container.requirements] |
Requirements on iterators of member template functions of containers |
Yes |
|
536 |
| 675 |
CD1 |
21.2 [container.requirements] |
Move assignment of containers |
Yes |
|
|
| 759 |
CD1 |
21.2 [container.requirements] |
A reference is not an object |
Yes |
|
|
| 766 |
CD1 |
21.2 [container.requirements] |
Inconsistent exception guarantees between ordered and unordered associative containers |
Yes |
|
|
| 842 |
CD1 |
21.2 [container.requirements] |
ConstructibleAsElement and bit containers |
Yes |
|
|
| 51 |
TC1 |
21.2 [container.requirements] |
Requirement to not invalidate iterators missing |
Yes |
|
|
| 760 |
NAD |
21.2 [container.requirements] |
The emplace issue |
Yes |
2 |
|
| 279 |
NAD |
21.2 [container.requirements] |
const and non-const iterators should have equivalent typedefs |
Yes |
|
|
| 632 |
NAD |
21.2 [container.requirements] |
Time complexity of size() for std::set |
Yes |
|
|
| 1330 |
NAD |
21.2 [container.requirements] |
Move container requirements into requirements tables |
Yes |
|
|
| 479 |
Dup |
21.2 [container.requirements] |
Container requirements and placement new |
Yes |
|
580 |
| 536 |
Dup |
21.2 [container.requirements] |
Container iterator constructor and explicit convertibility |
Yes |
|
589 |
| 3028 |
New |
21.2.1 [container.requirements.general] |
Container requirements tables should distinguish const and non-const variables |
Yes |
3 |
|
| 2269 |
New |
21.2.1 [container.requirements.general] |
Container iterators and argument-dependent lookup |
No |
4 |
|
| 2321 |
Open |
21.2.1 [container.requirements.general] |
Moving containers should (usually) be required to preserve iterators |
Yes |
3 |
|
| 1521 |
Open |
21.2.1 [container.requirements.general] |
Requirements on internal pointer representations in containers |
Yes |
|
|
| 2218 |
C++17 |
21.2.1 [container.requirements.general] |
Unclear how containers use allocator_traits::construct() |
Yes |
3 |
|
| 2448 |
C++17 |
21.2.1 [container.requirements.general] |
Non-normative Container destructor specification |
Yes |
0 |
|
| 2794 |
C++17 |
21.2.1 [container.requirements.general] |
Missing requirements for allocator pointers |
Yes |
0 |
|
| 2177 |
C++14 |
21.2.1 [container.requirements.general] |
Requirements on Copy/MoveInsertable |
Yes |
|
|
| 2182 |
C++14 |
21.2.1 [container.requirements.general] |
Container::[const_]reference types are misleadingly specified |
Yes |
0 |
|
| 2308 |
C++14 |
21.2.1 [container.requirements.general] |
Clarify container destructor requirements w.r.t. std::array |
Yes |
0 |
|
| 2320 |
C++14 |
21.2.1 [container.requirements.general] |
select_on_container_copy_construction() takes allocators, not containers |
Yes |
0 |
|
| 2105 |
C++14 |
21.2.1 [container.requirements.general] |
Inconsistent requirements on const_iterator's value_type |
Yes |
|
|
| 2211 |
C++14 |
21.2.1 [container.requirements.general] |
Replace ambiguous use of "Allocator" in container requirements |
Yes |
|
|
| 2257 |
C++14 |
21.2.1 [container.requirements.general] |
Simplify container requirements with the new algorithms |
Yes |
|
|
| 1034 |
C++11 |
21.2.1 [container.requirements.general] |
Clarify generality of Container Requirement tables |
Yes |
|
|
| 1319 |
C++11 |
21.2.1 [container.requirements.general] |
Containers should require an iterator that is at least a Forward Iterator |
Yes |
|
|
| 985 |
Resolved |
21.2.1 [container.requirements.general] |
Allowing throwing move |
Yes |
|
|
| 580 |
NAD Editorial |
21.2.1 [container.requirements.general] |
unused allocator members |
Yes |
|
479 |
| 1415 |
NAD Editorial |
21.2.1 [container.requirements.general] |
Iterator stability bans the short-string optimization |
Yes |
|
|
| 1035 |
NAD |
21.2.1 [container.requirements.general] |
<array>::swap can invalidate references, pointers, and iterators |
Yes |
|
|
| 2167 |
NAD |
21.2.1 [container.requirements.general] |
Copy assignment requirements of Containers |
Yes |
|
|
| 2200 |
C++14 |
21.2.2 [container.requirements.dataraces] |
Data race avoidance for all containers, not only for sequences |
Yes |
|
|
| 1329 |
Resolved |
21.2.2 [container.requirements.dataraces] |
Data races on vector<bool> |
Yes |
|
|
| 2705 |
New |
21.2.3 [sequence.reqmts] |
Questionable precondition on Sequence containers a.assign(n, t) |
Yes |
3 |
|
| 2206 |
Open |
21.2.3 [sequence.reqmts] |
Inaccuracy in initializer_list constructor requirements |
No |
3 |
|
| 2266 |
C++17 |
21.2.3 [sequence.reqmts] |
vector and deque have incorrect insert requirements |
Yes |
2 |
|
| 2698 |
C++17 |
21.2.3 [sequence.reqmts] |
Effect of assign() on iterators/pointers/references |
Yes |
0 |
|
| 2231 |
C++14 |
21.2.3 [sequence.reqmts] |
DR 704 removes complexity guarantee for clear() |
Yes |
|
|
| 149 |
C++11 |
21.2.3 [sequence.reqmts] |
Insert should return iterator to first element inserted |
Yes |
|
|
| 1037 |
C++11 |
21.2.3 [sequence.reqmts] |
Unclear status of match_results as library container |
Yes |
|
|
| 1038 |
C++11 |
21.2.3 [sequence.reqmts] |
Sequence requirement table needs to reference several new containers |
Yes |
|
|
| 1039 |
C++11 |
21.2.3 [sequence.reqmts] |
Sequence container back function should also support const_iterator |
Yes |
|
|
| 1234 |
C++11 |
21.2.3 [sequence.reqmts] |
"Do the right thing" and NULL |
Yes |
|
|
| 355 |
CD1 |
21.2.3 [sequence.reqmts] |
Operational semantics for a.back() |
Yes |
|
|
| 438 |
CD1 |
21.2.3 [sequence.reqmts] |
Ambiguity in the "do the right thing" clause |
Yes |
|
|
| 139 |
TC1 |
21.2.3 [sequence.reqmts] |
Optional sequence operation table description unclear |
Yes |
|
|
| 151 |
TC1 |
21.2.3 [sequence.reqmts] |
Can't currently clear() empty container |
Yes |
|
|
| 725 |
NAD Editorial |
21.2.3 [sequence.reqmts] |
Optional sequence container requirements column label |
Yes |
|
|
| 1058 |
NAD Editorial |
21.2.3 [sequence.reqmts] |
New container issue |
Yes |
|
|
| 1301 |
NAD Editorial |
21.2.3 [sequence.reqmts] |
clear() and assignment |
Yes |
|
|
| 526 |
NAD |
21.2.3 [sequence.reqmts] |
Is it undefined if a function in the standard changes in parameters? |
Yes |
|
|
| 1259 |
NAD |
21.2.3 [sequence.reqmts] |
Should initializer-list constructors move elements? |
Yes |
|
|
| 1036 |
NAD Concepts |
21.2.3 [sequence.reqmts] |
Remove iterator specification that is redundant due to concept constraints |
Yes |
|
|
| 2743 |
New |
21.2.4.1 [container.node.overview] |
p0083r3 node_handle private members missing "exposition only" comment |
No |
3 |
|
| 2362 |
New |
21.2.6 [associative.reqmts] |
unique, associative emplace() should not move/copy the mapped_type constructor
arguments when no insertion happens |
No |
3 |
|
| 2844 |
New |
21.2.6 [associative.reqmts] |
Stability of a_uniq.insert(i, j) |
No |
3 |
|
| 2215 |
Open |
21.2.6 [associative.reqmts] |
(unordered) associative container functors should be CopyConstructible |
Yes |
3 |
|
| 2227 |
Open |
21.2.6 [associative.reqmts] |
Stateful comparison objects in associative containers |
No |
3 |
|
| 2436 |
C++17 |
21.2.6 [associative.reqmts] |
Comparators for associative containers should always be CopyConstructible |
Yes |
2 |
|
| 2542 |
C++17 |
21.2.6 [associative.reqmts] |
Missing const requirements for associative containers |
Yes |
1 |
|
| 2322 |
C++14 |
21.2.6 [associative.reqmts] |
Associative(initializer_list, stuff) constructors are underspecified |
Yes |
0 |
|
| 1214 |
C++14 |
21.2.6 [associative.reqmts] |
Insufficient/inconsistent key immutability requirements for associative containers |
Yes |
|
|
| 2258 |
C++14 |
21.2.6 [associative.reqmts] |
a.erase(q1, q2) unable to directly return q2 |
Yes |
0 |
|
| 2299 |
C++14 |
21.2.6 [associative.reqmts] |
[CD] Effects of inaccessible key_compare::is_transparent type are not clear |
Yes |
1 |
|
| 982 |
C++11 |
21.2.6 [associative.reqmts] |
Wrong complexity for initializer_list assignment in Table 85 |
Yes |
|
|
| 1040 |
C++11 |
21.2.6 [associative.reqmts] |
Clarify possible sameness of associative container's iterator and const_iterator |
Yes |
|
|
| 1253 |
C++11 |
21.2.6 [associative.reqmts] |
invalidation of iterators and emplace vs. insert inconsistence in assoc. containers |
Yes |
|
|
| 103 |
CD1 |
21.2.6 [associative.reqmts] |
set::iterator is required to be modifiable, but this allows modification of keys |
Yes |
|
|
| 130 |
CD1 |
21.2.6 [associative.reqmts] |
Return type of container::erase(iterator) differs for associative containers |
Yes |
|
451 |
| 233 |
CD1 |
21.2.6 [associative.reqmts] |
Insertion hints in associative containers |
Yes |
|
192, 246 |
| 264 |
CD1 |
21.2.6 [associative.reqmts] |
Associative container insert(i, j) complexity requirements are not feasible. |
Yes |
|
102 |
| 316 |
CD1 |
21.2.6 [associative.reqmts] |
Vague text in Table 69 |
Yes |
|
|
| 354 |
CD1 |
21.2.6 [associative.reqmts] |
Associative container lower/upper bound requirements |
Yes |
|
|
| 224 |
TC1 |
21.2.6 [associative.reqmts] |
clear() complexity for associative containers refers to undefined N |
Yes |
|
|
| 1041 |
Resolved |
21.2.6 [associative.reqmts] |
Add associative/unordered container functions that allow to extract elements |
Yes |
|
|
| 2052 |
Resolved |
21.2.6 [associative.reqmts] |
Mixup between mapped_type and value_type for associative containers |
Yes |
2 |
|
| 2830 |
Resolved |
21.2.6 [associative.reqmts] |
insert_return_type is only defined for containers with unique keys |
Yes |
|
|
| 2430 |
NAD |
21.2.6 [associative.reqmts] |
Heterogeneous container lookup should be enabled using meta-function instead of nested type |
Yes |
|
|
| 2772 |
NAD |
21.2.6 [associative.reqmts] |
Inconsistency in the insert(node) interface |
Yes |
2 |
|
| 82 |
NAD |
21.2.6 [associative.reqmts] |
Missing constant for set elements |
Yes |
|
|
| 192 |
NAD |
21.2.6 [associative.reqmts] |
a.insert(p,t) is inefficient and overconstrained |
Yes |
|
233 |
| 215 |
NAD |
21.2.6 [associative.reqmts] |
Can a map's key_type be const? |
Yes |
|
|
| 494 |
NAD |
21.2.6 [associative.reqmts] |
Wrong runtime complexity for associative container's insert and delete |
Yes |
|
|
| 763 |
NAD |
21.2.6 [associative.reqmts] |
Renaming emplace() overloads |
Yes |
|
|
| 1302 |
NAD |
21.2.6 [associative.reqmts] |
different emplace semantics for sequence and associated containers |
Yes |
|
|
| 102 |
Dup |
21.2.6 [associative.reqmts] |
Bug in insert range in associative containers |
Yes |
|
264 |
| 246 |
Dup |
21.2.6 [associative.reqmts] |
a.insert(p,t) is incorrectly specified |
Yes |
|
233 |
| 451 |
Dup |
21.2.6 [associative.reqmts] |
Associative erase should return an iterator |
Yes |
|
130 |
| 1188 |
Tentatively NAD |
21.2.7 [unord.req] |
Unordered containers should have a minimum load factor as well as a maximum |
Yes |
|
|
| 1175 |
Open |
21.2.7 [unord.req] |
unordered complexity |
Yes |
3 |
|
| 2198 |
Open |
21.2.7 [unord.req] |
max_load_factor(z) makes no strong guarantees, but bans useful behavior |
Yes |
3 |
|
| 2977 |
WP |
21.2.7 [unord.req] |
unordered_meow::merge() has incorrect Throws: clause |
Yes |
0 |
|
| 2156 |
C++17 |
21.2.7 [unord.req] |
Unordered containers' reserve(n) reserves for n-1 elements |
Yes |
3 |
|
| 2540 |
C++17 |
21.2.7 [unord.req] |
unordered_multimap::insert hint iterator |
Yes |
3 |
|
| 2550 |
C++17 |
21.2.7 [unord.req] |
Wording of unordered container's clear() method complexity |
Yes |
2 |
|
| 2304 |
C++14 |
21.2.7 [unord.req] |
Complexity of count in unordered associative containers |
Yes |
0 |
|
| 2356 |
C++14 |
21.2.7 [unord.req] |
Stability of erasure in unordered associative containers |
Yes |
2 |
|
| 869 |
C++11 |
21.2.7 [unord.req] |
Bucket (local) iterators and iterating past end |
Yes |
|
|
| 870 |
C++11 |
21.2.7 [unord.req] |
Do unordered containers not support function pointers for predicate/hasher? |
Yes |
|
|
| 981 |
C++11 |
21.2.7 [unord.req] |
Unordered container requirements should add initializer_list support |
Yes |
|
|
| 1189 |
C++11 |
21.2.7 [unord.req] |
Awkward interface for changing the number of buckets in an unordered associative container |
Yes |
|
|
| 1197 |
C++11 |
21.2.7 [unord.req] |
Can unordered containers have bucket_count() == 0? |
Yes |
|
|
| 518 |
CD1 |
21.2.7 [unord.req] |
Are insert and erase stable for unordered_multiset and unordered_multimap? |
Yes |
|
|
| 2831 |
Resolved |
21.2.7 [unord.req] |
Equality can be defined when Hash function objects have different behaviour |
Yes |
|
|
| 579 |
NAD |
21.2.7 [unord.req] |
erase(iterator) for unordered containers should not return an iterator |
Yes |
|
|
| 764 |
NAD |
21.2.7 [unord.req] |
equal_range on unordered containers should return a pair of local_iterators |
Yes |
|
|
| 1190 |
NAD |
21.2.7 [unord.req] |
Setting the maximum load factor should return the previous value |
Yes |
|
|
| 2006 |
NAD |
21.2.7 [unord.req] |
emplace broken for associative containers |
Yes |
|
|
| 2199 |
NAD |
21.2.7 [unord.req] |
unordered containers are required to have an initial max load factor of 1.0 |
Yes |
3 |
|
| 2189 |
Open |
21.2.7.1 [unord.req.except] |
Throwing swap breaks unordered containers' state |
No |
3 |
|
| 2209 |
C++14 |
21.3 [sequences] |
assign() overspecified for sequence containers |
Yes |
|
|
| 2210 |
C++14 |
21.3 [sequences] |
Missing allocator-extended constructor for allocator-aware containers |
Yes |
|
|
| 679 |
CD1 |
21.3 [sequences] |
resize parameter by value |
Yes |
|
|
| 1042 |
NAD |
21.3 [sequences] |
Provide ContiguousStorage concept and apply it to corresponding containers |
Yes |
|
|
| 2427 |
C++17 |
21.3.1 [sequences.general] |
Container adaptors as sequence containers, redux |
Yes |
0 |
|
| 2914 |
Resolved |
21.3.2 [array.syn] |
std::array does not support class-template deduction from initializers |
Yes |
|
|
| 2335 |
New |
21.3.7 [array] |
array<array<int, 3>, 4> should be layout-compatible with int[4][3] |
No |
3 |
|
| 1306 |
C++11 |
21.3.7 [array] |
pointer and const_pointer for <array> |
Yes |
|
|
| 519 |
CD1 |
21.3.7 [array] |
Data() undocumented |
Yes |
|
|
| 720 |
CD1 |
21.3.7 [array] |
Omissions in constexpr usages |
Yes |
|
|
| 776 |
CD1 |
21.3.7 [array] |
Undescribed assign function of std::array |
Yes |
|
|
| 2443 |
Resolved |
21.3.7 [array] |
std::array member functions should be constexpr |
Yes |
|
|
| 851 |
NAD |
21.3.7 [array] |
simplified array construction |
Yes |
|
|
| 588 |
NAD |
21.3.7 [array] |
requirements on zero sized tr1::arrays and other details |
Yes |
|
|
| 617 |
NAD |
21.3.7 [array] |
std::array is a sequence that doesn't satisfy the sequence requirements? |
Yes |
|
|
| 930 |
NAD |
21.3.7 [array] |
Access to std::array data as built-in array type |
Yes |
|
|
| 2823 |
Open |
21.3.7.1 [array.overview] |
std::array initialization is still not permissive enough |
Yes |
3 |
|
| 2310 |
C++17 |
21.3.7.1 [array.overview] |
Public exposition only member in std::array |
Yes |
4 |
|
| 2590 |
C++17 |
21.3.7.1 [array.overview] |
Aggregate initialization for std::array |
Yes |
0 |
|
| 2897 |
Resolved |
21.3.7.1 [array.overview] |
array::iterator and array::const_iterator should be literal types |
Yes |
2 |
|
| 2157 |
Open |
21.3.7.5 [array.zero] |
How does std::array<T,0> initialization work when T is not default-constructible? |
Yes |
3 |
|
| 1417 |
C++11 |
21.3.7.5 [array.zero] |
front/back on a zero-sized array should be undefined |
Yes |
|
|
| 237 |
CD1 |
21.3.8.2 [deque.cons] |
Undefined expression in complexity specification |
Yes |
|
|
| 144 |
TC1 |
21.3.8.2 [deque.cons] |
Deque constructor complexity wrong |
Yes |
|
|
| 1418 |
C++11 |
21.3.8.3 [deque.capacity] |
Effects of resize(size()) on a deque |
Yes |
|
|
| 850 |
CD1 |
21.3.8.3 [deque.capacity] |
Should shrink_to_fit apply to std::deque? |
Yes |
|
|
| 855 |
NAD |
21.3.8.3 [deque.capacity] |
capacity() and reserve() for deque? |
Yes |
|
|
| 2953 |
WP |
21.3.8.4 [deque.modifiers] |
LWG 2853 should apply to deque::erase too |
Yes |
0 |
|
| 2364 |
C++17 |
21.3.8.4 [deque.modifiers] |
deque and vector pop_back don't specify iterator invalidation requirements |
Yes |
0 |
|
| 2477 |
C++17 |
21.3.8.4 [deque.modifiers] |
Inconsistency of wordings in std::vector::erase() and std::deque::erase() |
Yes |
0 |
|
| 638 |
CD1 |
21.3.8.4 [deque.modifiers] |
deque end invalidation during erase |
Yes |
|
|
| 878 |
C++11 |
21.3.9 [forwardlist] |
forward_list preconditions |
Yes |
|
|
| 1276 |
C++11 |
21.3.9 [forwardlist] |
forwardlist missing allocator constructors |
Yes |
|
|
| 1419 |
NAD Editorial |
21.3.9 [forwardlist] |
forward_list::erase_after should return an iterator |
Yes |
|
|
| 2042 |
C++11 |
21.3.9.3 [forwardlist.iter] |
Comparing forward_list::before_begin() to forward_list::end() |
Yes |
|
|
| 2585 |
C++17 |
21.3.9.5 [forwardlist.modifiers] |
forward_list::resize(size_type, const value_type&) effects incorrect |
Yes |
0 |
|
| 1278 |
C++11 |
21.3.9.5 [forwardlist.modifiers] |
Inconsistent return values for forward_list::insert_after |
Yes |
|
|
| 1340 |
C++11 |
21.3.9.5 [forwardlist.modifiers] |
Why does forward_list::resize take the object to be copied by value? |
Yes |
|
|
| 897 |
Resolved |
21.3.9.5 [forwardlist.modifiers] |
Forward_list issues... Part 2 |
Yes |
|
|
| 3088 |
New |
21.3.9.6 [forwardlist.ops] |
forward_list::merge behavior unclear when passed *this |
Yes |
3 |
|
| 3017 |
WP |
21.3.9.6 [forwardlist.ops] |
list splice functions should use addressof |
Yes |
0 |
|
| 2045 |
C++14 |
21.3.9.6 [forwardlist.ops] |
forward_list::merge and forward_list::splice_after with unequal allocators |
Yes |
|
|
| 2123 |
C++14 |
21.3.9.6 [forwardlist.ops] |
merge() allocator requirements for lists versus forward lists |
Yes |
|
|
| 2222 |
C++14 |
21.3.9.6 [forwardlist.ops] |
Inconsistency in description of forward_list::splice_after single-element overload |
Yes |
|
|
| 898 |
C++11 |
21.3.9.6 [forwardlist.ops] |
Small contradiction in n2723 to forward to committee |
Yes |
|
|
| 1133 |
C++11 |
21.3.9.6 [forwardlist.ops] |
Does N2844 break current specification of list::splice? |
Yes |
|
|
| 1310 |
C++11 |
21.3.9.6 [forwardlist.ops] |
forward_list splice_after from lvalues |
Yes |
|
|
| 892 |
NAD Editorial |
21.3.9.6 [forwardlist.ops] |
Forward_list issues... |
Yes |
|
|
| 919 |
NAD |
21.3.9.6 [forwardlist.ops] |
(forward_)list specialized remove algorithms are over constrained |
Yes |
|
|
| 307 |
CD1 |
21.3.10 [list] |
Lack of reference typedefs in container adaptors |
Yes |
|
|
| 320 |
CD1 |
21.3.10.2 [list.cons] |
list::assign overspecified |
Yes |
|
|
| 410 |
CD1 |
21.3.10.2 [list.cons] |
Missing semantics for stack and queue comparison operators |
Yes |
|
|
| 1420 |
C++11 |
21.3.10.3 [list.capacity] |
Effects of resize(size()) on a list |
Yes |
|
|
| 132 |
TC1 |
21.3.10.3 [list.capacity] |
list::resize description uses random access iterators |
Yes |
|
|
| 3087 |
Tentatively Ready |
21.3.10.5 [list.ops] |
One final &x in §[list.ops] |
Yes |
3 |
|
| 2997 |
New |
21.3.10.5 [list.ops] |
LWG 491 and the specification of {forward_,}list::unique |
Yes |
3 |
|
| 2998 |
WP |
21.3.10.5 [list.ops] |
Requirements on function objects passed to {forward_,}list-specific algorithms |
Yes |
0 |
|
| 2824 |
C++17 |
21.3.10.5 [list.ops] |
list::sort should say that the order of elements is unspecified if an exception is thrown |
Yes |
0 |
|
| 2122 |
C++14 |
21.3.10.5 [list.ops] |
merge() stability for lists versus forward lists |
Yes |
|
|
| 1207 |
C++11 |
21.3.10.5 [list.ops] |
Underspecified std::list operations? |
Yes |
|
|
| 1215 |
C++11 |
21.3.10.5 [list.ops] |
list::merge with unequal allocators |
Yes |
|
|
| 250 |
CD1 |
21.3.10.5 [list.ops] |
splicing invalidates iterators |
Yes |
|
|
| 278 |
CD1 |
21.3.10.5 [list.ops] |
What does iterator validity mean? |
Yes |
|
|
| 300 |
CD1 |
21.3.10.5 [list.ops] |
list::merge() specification incomplete |
Yes |
|
|
| 315 |
CD1 |
21.3.10.5 [list.ops] |
Bad "range" in list::unique complexity |
Yes |
|
|
| 131 |
NAD |
21.3.10.5 [list.ops] |
list::splice throws nothing |
Yes |
|
|
| 491 |
NAD |
21.3.10.5 [list.ops] |
std::list<>::unique incorrectly specified |
Yes |
|
|
| 2279 |
NAD |
21.3.10.5 [list.ops] |
Carefully state effects of list::splice function |
Yes |
|
|
| 464 |
CD1 |
21.3.11 [vector] |
Suggestion for new member functions in standard containers |
Yes |
|
|
| 469 |
CD1 |
21.3.11 [vector] |
vector<bool> ill-formed relational operators |
Yes |
|
|
| 496 |
CD1 |
21.3.11 [vector] |
Illegal use of "T" in vector<bool> |
Yes |
|
|
| 69 |
TC1 |
21.3.11 [vector] |
Must elements of a vector be contiguous? |
Yes |
|
|
| 101 |
NAD Editorial |
21.3.11 [vector] |
No way to free storage for vector and deque |
Yes |
|
|
| 757 |
NAD Editorial |
21.3.11 [vector] |
Typo in the synopsis of vector |
Yes |
|
|
| 1184 |
NAD |
21.3.11 [vector] |
Feature request: dynamic bitset |
Yes |
|
|
| 96 |
NAD |
21.3.11 [vector] |
Vector<bool> is not a container |
Yes |
|
|
| 134 |
TC1 |
21.3.11.2 [vector.cons] |
vector constructors over specified |
Yes |
|
|
| 2158 |
Open |
21.3.11.3 [vector.capacity] |
Conditional copy/move in std::vector |
Yes |
3 |
|
| 2160 |
C++17 |
21.3.11.3 [vector.capacity] |
Unintended destruction ordering-specification of resize |
Yes |
1 |
|
| 2223 |
C++17 |
21.3.11.3 [vector.capacity] |
shrink_to_fit effect on iterator validity |
Yes |
2 |
|
| 2323 |
C++14 |
21.3.11.3 [vector.capacity] |
vector::resize(n, t)'s specification should be simplified |
Yes |
0 |
|
| 2033 |
C++14 |
21.3.11.3 [vector.capacity] |
Preconditions of reserve, shrink_to_fit, and resize functions |
Yes |
|
|
| 1525 |
C++11 |
21.3.11.3 [vector.capacity] |
Effects of resize(size()) on a vector |
Yes |
|
|
| 329 |
CD1 |
21.3.11.3 [vector.capacity] |
vector capacity, reserve and reallocation |
Yes |
|
|
| 341 |
CD1 |
21.3.11.3 [vector.capacity] |
Vector reallocation and swap |
Yes |
|
|
| 755 |
CD1 |
21.3.11.3 [vector.capacity] |
std::vector and std:string lack explicit shrink-to-fit operations |
Yes |
|
|
| 2066 |
Resolved |
21.3.11.3 [vector.capacity] |
Missing specification of vector::resize(size_type) |
Yes |
|
|
| 1102 |
NAD |
21.3.11.3 [vector.capacity] |
std::vector's reallocation policy still unclear |
Yes |
|
|
| 1246 |
NAD |
21.3.11.3 [vector.capacity] |
vector::resize() missing efficiency guarantee |
Yes |
|
|
| 2596 |
C++17 |
21.3.11.4 [vector.data] |
vector::data() should use addressof |
Yes |
0 |
|
| 1312 |
C++11 |
21.3.11.4 [vector.data] |
vector::data no longer returns a raw pointer |
Yes |
|
|
| 3077 |
New |
21.3.11.5 [vector.modifiers] |
(push|emplace)_back should invalidate the end iterator |
Yes |
3 |
|
| 2164 |
WP |
21.3.11.5 [vector.modifiers] |
What are the semantics of vector.emplace(vector.begin(), vector.back())? |
Yes |
2 |
|
| 2853 |
C++17 |
21.3.11.5 [vector.modifiers] |
Possible inconsistency in specification of erase in [vector.modifiers] |
Yes |
0 |
|
| 2252 |
C++14 |
21.3.11.5 [vector.modifiers] |
Strong guarantee on vector::push_back() still broken with C++11? |
Yes |
|
|
| 247 |
CD1 |
21.3.11.5 [vector.modifiers] |
vector, deque::insert complexity |
Yes |
|
|
| 406 |
CD1 |
21.3.11.5 [vector.modifiers] |
vector::insert(s) exception safety |
Yes |
|
|
| 414 |
CD1 |
21.3.11.5 [vector.modifiers] |
Which iterators are invalidated by v.erase()? |
Yes |
|
|
| 2256 |
NAD |
21.3.11.5 [vector.modifiers] |
On vector iterator invalidation |
Yes |
3 |
|
| 2449 |
NAD |
21.3.11.5 [vector.modifiers] |
vector::insert invalidates end()? |
Yes |
3 |
|
| 1422 |
Open |
21.3.12 [vector.bool] |
vector<bool> iterators are not random access |
No |
3 |
|
| 2187 |
C++14 |
21.3.12 [vector.bool] |
vector<bool> is missing emplace and emplace_back member functions |
Yes |
|
|
| 814 |
C++11 |
21.3.12 [vector.bool] |
vector<bool>::swap(reference, reference) not defined |
Yes |
|
|
| 1254 |
C++11 |
21.3.12 [vector.bool] |
Misleading sentence in vector<bool>::flip |
Yes |
|
|
| 1284 |
C++11 |
21.3.12 [vector.bool] |
vector<bool> initializer_list constructor missing an allocator argument |
Yes |
|
|
| 751 |
NAD |
21.3.12 [vector.bool] |
change pass-by-reference members of vector<bool> to pass-by-value? |
Yes |
|
|
| 839 |
Resolved |
21.4 [associative] |
Maps and sets missing splice operation |
Yes |
|
|
| 2012 |
Resolved |
21.4 [associative] |
Associative maps should insert pair, not tuple |
Yes |
|
|
| 2161 |
NAD |
21.4 [associative] |
const equivalence of std::map |
Yes |
2 |
|
| 1111 |
NAD Concepts |
21.4 [associative] |
associative containers underconstrained |
Yes |
|
|
| 2059 |
C++17 |
21.4.4 [map] |
C++0x ambiguity problem with map::erase |
Yes |
3 |
|
| 2300 |
C++14 |
21.4.4 [map] |
[CD] Redundant sections for map and multimap members should be removed |
Yes |
|
|
| 1423 |
C++11 |
21.4.4 [map] |
map constructor accepting an allocator as single parameter should be explicit |
Yes |
|
|
| 133 |
TC1 |
21.4.4 [map] |
map missing get_allocator() |
Yes |
|
|
| 140 |
NAD Editorial |
21.4.4 [map] |
map<Key, T>::value_type does not satisfy the assignable requirement |
Yes |
|
|
| 1296 |
NAD |
21.4.4 [map] |
map and multimap value_compare overspecified |
Yes |
|
|
| 3025 |
WP |
21.4.4.1 [map.overview] |
Map-like container deduction guides should use pair<Key, T>, not pair<const Key, T> |
Yes |
2 |
|
| 2354 |
C++17 |
21.4.4.1 [map.overview] |
Unnecessary copying when inserting into maps with braced-init syntax |
Yes |
2 |
|
| 2469 |
C++17 |
21.4.4.3 [map.access] |
Wrong specification of Requires clause of operator[] for map and unordered_map |
Yes |
3 |
|
| 2007 |
C++11 |
21.4.4.3 [map.access] |
Incorrect specification of return value for map<>::at() |
Yes |
|
|
| 334 |
CD1 |
21.4.4.3 [map.access] |
map::operator[] specification forces inefficient implementation |
Yes |
|
|
| 703 |
CD1 |
21.4.4.3 [map.access] |
map::at() need a complexity specification |
Yes |
|
|
| 2274 |
Resolved |
21.4.4.3 [map.access] |
Does map::operator[] value-initialize or default-insert a missing element? |
Yes |
3 |
|
| 2464 |
C++17 |
21.4.4.4 [map.modifiers] |
try_emplace and insert_or_assign misspecified |
Yes |
2 |
|
| 2571 |
C++17 |
21.4.4.4 [map.modifiers] |
§[map.modifiers]/2 imposes nonsensical requirement on insert(InputIterator, InputIterator) |
Yes |
0 |
|
| 2005 |
C++14 |
21.4.4.4 [map.modifiers] |
unordered_map::insert(T&&) protection should apply to map too |
Yes |
|
|
| 1424 |
C++11 |
21.4.5 [multimap] |
multimap constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 1091 |
NAD |
21.4.5.3 [multimap.modifiers] |
Multimap description confusing |
Yes |
|
|
| 1425 |
C++11 |
21.4.6 [set] |
set constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 214 |
CD1 |
21.4.6 [set] |
set::find() missing const overload |
Yes |
|
450 |
| 450 |
Dup |
21.4.6 [set] |
set::find is inconsistent with associative container requirements |
Yes |
|
214 |
| 2076 |
C++17 |
21.4.6.2 [set.cons] |
Bad CopyConstructible requirement in set constructors |
Yes |
3 |
|
| 1426 |
C++11 |
21.4.7 [multiset] |
multiset constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 2713 |
New |
21.5 [unord] |
More missing allocator-extended constructors for unordered containers |
Yes |
3 |
|
| 2230 |
C++17 |
21.5 [unord] |
"see below" for initializer-list constructors of unordered containers |
Yes |
4 |
|
| 2050 |
C++14 |
21.5 [unord] |
Unordered associative containers do not use allocator_traits to define member types |
Yes |
|
|
| 676 |
C++11 |
21.5 [unord] |
Moving the unordered containers |
Yes |
|
|
| 691 |
CD1 |
21.5 [unord] |
const_local_iterator cbegin, cend missing from TR1 |
Yes |
|
|
| 852 |
CD1 |
21.5 [unord] |
unordered containers begin(n) mistakenly const |
Yes |
|
|
| 1248 |
Resolved |
21.5 [unord] |
Equality comparison for unordered containers |
Yes |
|
|
| 528 |
NAD |
21.5 [unord] |
const_iterator iterator issue when they are the same type |
Yes |
|
|
| 2026 |
NAD |
21.5 [unord] |
hash should be std qualified for unordered container |
Yes |
|
|
| 1427 |
C++11 |
21.5.4 [unord.map] |
unordered_map constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 1519 |
C++11 |
21.5.4 [unord.map] |
bucketsize() const only for unordered set |
Yes |
|
|
| 761 |
CD1 |
21.5.4.3 [unord.map.elem] |
unordered_map needs an at() member function |
Yes |
|
|
| 1428 |
C++11 |
21.5.5 [unord.multimap] |
unordered_multimap constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 1429 |
C++11 |
21.5.6 [unord.set] |
unordered_set constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 2982 |
WP |
21.5.6.1 [unord.set.overview] |
Making size_type consistent in associative container deduction guides |
Yes |
2 |
|
| 1430 |
C++11 |
21.5.7 [unord.multiset] |
unordered_multiset constructor accepting an allocator as a single parameter should be explicit |
Yes |
|
|
| 2566 |
C++17 |
21.6 [container.adaptors] |
Requirements on the first template parameter of container adaptors |
Yes |
0 |
|
| 2194 |
C++14 |
21.6 [container.adaptors] |
Impossible container requirements for adaptor types |
Yes |
|
|
| 1194 |
C++11 |
21.6 [container.adaptors] |
Unintended queue constructor |
Yes |
|
|
| 1198 |
C++11 |
21.6 [container.adaptors] |
Container adaptor swap: member or non-member? |
Yes |
|
|
| 1199 |
C++11 |
21.6 [container.adaptors] |
Missing extended copy constructor in container adaptors |
Yes |
|
|
| 2915 |
Resolved |
21.6 [container.adaptors] |
The three container adapters should each have a deduction guide |
Yes |
|
|
| 756 |
Resolved |
21.6 [container.adaptors] |
Container adaptors push |
Yes |
|
|
| 1421 |
Resolved |
21.6 [container.adaptors] |
Accidental move-only library types due to new core language rules |
Yes |
|
1350 |
| 2783 |
WP |
21.6.4.1 [queue.defn] |
stack::emplace() and queue::emplace() should return decltype(auto) |
Yes |
2 |
|
| 2684 |
C++17 |
21.6.5 [priority.queue] |
priority_queue lacking comparator typedef |
Yes |
0 |
|
| 2552 |
NAD |
21.6.5 [priority.queue] |
priority_queue doesn't work with move-only types |
Yes |
3 |
|
| 1196 |
Resolved |
21.6.5.2 [priqueue.cons] |
move semantics undefined for priority_queue |
Yes |
|
|
| 2537 |
C++17 |
21.6.5.3 [priqueue.cons.alloc] |
Constructors for priority_queue taking allocators should call make_heap |
Yes |
0 |
|
| 3161 |
New |
21.6.6 [stack] |
Container adapters mandate use of emplace_back but don't require it |
Yes |
|
|
| 1186 |
NAD Concepts |
21.6.6 [stack] |
Forward list could model a stack |
Yes |
|
|
| 976 |
Resolved |
21.6.6.1 [stack.defn] |
Class template std::stack should be movable |
Yes |
|
|
| 3144 |
New |
21.7.3.1 [span.overview] |
span does not have a const_pointer typedef |
Yes |
|
|
| 3102 |
WP |
21.7.3.1 [span.overview] |
Clarify span iterator and const_iterator behavior |
Yes |
0 |
|
| 3101 |
Tentatively Ready |
21.7.3.2 [span.cons] |
span's Container constructors need another constraint |
Yes |
1 |
|
| 3100 |
WP |
21.7.3.2 [span.cons] |
Unnecessary and confusing "empty span" wording |
Yes |
0 |
|
| 3103 |
Open |
21.7.3.3 [span.sub] |
Errors in taking subview of span should be ill-formed where possible |
Yes |
3 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 2061 |
C++14 |
22.2 [iterator.synopsis] |
make_move_iterator and arrays |
Yes |
|
|
| 2128 |
C++14 |
22.2 [iterator.synopsis] |
Absence of global functions cbegin/cend |
Yes |
|
|
| 1320 |
NAD |
22.2 [iterator.synopsis] |
Header for iter_swap |
Yes |
|
|
| 1213 |
Open |
22.3 [iterator.requirements] |
Meaning of valid and singular iterator underspecified |
No |
4 |
|
| 2578 |
C++17 |
22.3 [iterator.requirements] |
Iterator requirements should reference iterator traits |
Yes |
3 |
|
| 1185 |
Resolved |
22.3 [iterator.requirements] |
Iterator categories and output iterators |
Yes |
|
|
| 1210 |
Resolved |
22.3 [iterator.requirements] |
Iterator reachability should not require a container |
Yes |
|
|
| 1212 |
Resolved |
22.3 [iterator.requirements] |
result of post-increment/decrement operator |
Yes |
|
|
| 408 |
NAD Editorial |
22.3 [iterator.requirements] |
Is vector<reverse_iterator<char*> > forbidden? |
Yes |
|
|
| 446 |
NAD Editorial |
22.3 [iterator.requirements] |
Iterator equality between different containers |
Yes |
|
|
| 2107 |
NAD |
22.3 [iterator.requirements] |
Some iterator category should guarantee the lifetime of references |
Yes |
|
|
| 3110 |
New |
22.3.1 [iterator.requirements.general] |
Contiguous Iterators should always be Random-Access |
Yes |
3 |
|
| 2375 |
New |
22.3.1 [iterator.requirements.general] |
Is [iterator.requirements.general]/9 too broadly applied? |
No |
3 |
|
| 2951 |
New |
22.3.2.3 [iterator.traits] |
iterator_traits should SFINAE for void* and function pointers |
Yes |
3 |
|
| 2952 |
WP |
22.3.2.3 [iterator.traits] |
iterator_traits should work for pointers to cv T |
Yes |
0 |
|
| 445 |
CD1 |
22.3.2.3 [iterator.traits] |
iterator_traits::reference unspecified for some iterator categories |
Yes |
|
|
| 1127 |
NAD Concepts |
22.3.2.3 [iterator.traits] |
rvalue references and iterator traits |
Yes |
|
|
| 765 |
C++11 |
22.3.4 [iterator.concepts] |
More on iterator validity |
Yes |
|
|
| 198 |
CD1 |
22.3.4 [iterator.concepts] |
Validity of pointers and references unspecified after iterator destruction |
Yes |
|
|
| 346 |
CD1 |
22.3.4 [iterator.concepts] |
Some iterator member functions should be const |
Yes |
|
|
| 407 |
CD1 |
22.3.4 [iterator.concepts] |
Can singular iterators be destroyed? |
Yes |
|
|
| 208 |
TC1 |
22.3.4 [iterator.concepts] |
Unnecessary restriction on past-the-end iterators |
Yes |
|
|
| 304 |
NAD |
22.3.4 [iterator.concepts] |
Must *a return an lvalue when a is an input iterator? |
Yes |
|
|
| 2437 |
C++17 |
22.3.5.1 [iterator.iterators] |
iterator_traits<OutIt>::reference can and can't be void |
Yes |
3 |
|
| 1009 |
NAD |
22.3.5.1 [iterator.iterators] |
InputIterator post-increment dangerous |
Yes |
|
|
| 2962 |
Open |
22.3.5.2 [input.iterators] |
Iterators of Containers of move-only types do not model InputIterator |
Yes |
2 |
|
| 484 |
Open |
22.3.5.2 [input.iterators] |
Convertible to T |
No |
2 |
|
| 98 |
CD1 |
22.3.5.2 [input.iterators] |
Input iterator requirements are badly written |
Yes |
|
|
| 558 |
NAD Editorial |
22.3.5.2 [input.iterators] |
lib.input.iterators Defect |
Yes |
|
|
| 392 |
NAD |
22.3.5.2 [input.iterators] |
'equivalence' for input iterators |
Yes |
|
|
| 493 |
NAD |
22.3.5.2 [input.iterators] |
Undefined Expression in Input Iterator Note Title |
Yes |
|
|
| 2035 |
Open |
22.3.5.3 [output.iterators] |
Output iterator requirements are broken |
Yes |
3 |
|
| 2038 |
Open |
22.3.5.3 [output.iterators] |
Missing definition for incrementable iterator |
No |
3 |
|
| 324 |
CD1 |
22.3.5.3 [output.iterators] |
Do output iterators have value types? |
Yes |
|
|
| 485 |
Resolved |
22.3.5.3 [output.iterators] |
output iterator insufficiently constrained |
Yes |
|
|
| 200 |
CD1 |
22.3.5.4 [forward.iterators] |
Forward iterator requirements don't allow constant iterators |
Yes |
|
|
| 478 |
CD1 |
22.3.5.4 [forward.iterators] |
Should forward iterator requirements table have a line for r->m? |
Yes |
|
477 |
| 1311 |
Resolved |
22.3.5.4 [forward.iterators] |
multi-pass property of Forward Iterator underspecified |
Yes |
|
|
| 476 |
NAD |
22.3.5.4 [forward.iterators] |
Forward Iterator implied mutability |
Yes |
|
|
| 477 |
Dup |
22.3.5.4 [forward.iterators] |
Operator-> for const forward iterators |
Yes |
|
478 |
| 1084 |
NAD Concepts |
22.3.5.4 [forward.iterators] |
Concept ForwardIterator should provide default implementation for post-increment |
Yes |
|
|
| 383 |
CD1 |
22.3.5.5 [bidirectional.iterators] |
Bidirectional iterator assertion typo |
Yes |
|
|
| 299 |
NAD Editorial |
22.3.5.5 [bidirectional.iterators] |
Incorrect return types for iterator dereference |
Yes |
|
|
| 1085 |
NAD Concepts |
22.3.5.5 [bidirectional.iterators] |
BidirectionalIterator concept should provide default implementation for post-decrement |
Yes |
|
|
| 2519 |
C++17 |
22.3.5.6 [random.access.iterators] |
Iterator operator-= has gratuitous undefined behaviour |
Yes |
2 |
|
| 1079 |
C++11 |
22.3.5.6 [random.access.iterators] |
UK-265: RandomAccessIterator's operator- has nonsensical effects clause |
Yes |
|
|
| 448 |
CD1 |
22.3.5.6 [random.access.iterators] |
Random Access Iterators over abstract classes |
Yes |
|
|
| 458 |
NAD |
22.3.5.6 [random.access.iterators] |
24.1.5 contains unintended limitation for operator- |
Yes |
|
|
| 1010 |
NAD Concepts |
22.3.5.6 [random.access.iterators] |
operator-= should use default in concept |
Yes |
|
|
| 2931 |
Open |
22.4.2 [iterator.operations] |
Missed optimization opportunity with single-argument std::next |
No |
3 |
|
| 2353 |
C++17 |
22.4.2 [iterator.operations] |
std::next is over-constrained |
Yes |
4 |
|
| 1011 |
C++11 |
22.4.2 [iterator.operations] |
next/prev wrong iterator type |
Yes |
|
|
| 940 |
Resolved |
22.4.2 [iterator.operations] |
std::distance |
Yes |
|
|
| 204 |
NAD |
22.4.2 [iterator.operations] |
distance(first, last) when "last" is before "first" |
Yes |
|
|
| 2858 |
New |
22.5.1 [reverse.iterators] |
LWG 2472: actually an incompatibility with C++03 |
Yes |
4 |
|
| 2285 |
C++14 |
22.5.1 [reverse.iterators] |
make_reverse_iterator |
Yes |
|
|
| 280 |
CD1 |
22.5.1 [reverse.iterators] |
Comparison of reverse_iterator to const reverse_iterator |
Yes |
|
|
| 2208 |
Resolved |
22.5.1 [reverse.iterators] |
std::reverse_iterator should be a literal type |
Yes |
3 |
|
| 2595 |
New |
22.5.1.1 [reverse.iterator] |
reverse_iterator::operator[]'s return type revisited |
Yes |
3 |
|
| 2360 |
C++14 |
22.5.1.1 [reverse.iterator] |
reverse_iterator::operator*() is unimplementable |
Yes |
1 |
|
| 235 |
CD1 |
22.5.1.1 [reverse.iterator] |
No specification of default ctor for reverse_iterator |
Yes |
|
|
| 1012 |
C++11 |
22.5.1.3 [reverse.iter.cons] |
reverse_iterator default ctor should value initialize |
Yes |
|
|
| 2916 |
NAD |
22.5.2 [insert.iterators] |
Insert iterators should each have an instantiation guide to initialize from a container |
Yes |
|
|
| 100 |
NAD |
22.5.2 [insert.iterators] |
Insert iterators/ostream_iterators overconstrained |
Yes |
|
|
| 977 |
NAD |
22.5.2 [insert.iterators] |
insert iterators inefficient for expensive to move types |
Yes |
|
|
| 1062 |
NAD |
22.5.2 [insert.iterators] |
Missing insert_iterator for stacks/queues |
Yes |
|
|
| 903 |
NAD |
22.5.2.1 [back.insert.iterator] |
back_insert_iterator issue |
Yes |
|
|
| 901 |
NAD |
22.5.2.3 [insert.iterator] |
insert iterators can move from lvalues |
Yes |
|
|
| 561 |
CD1 |
22.5.2.3.2 [inserter] |
inserter overly generic |
Yes |
|
|
| 2106 |
C++17 |
22.5.3 [move.iterators] |
move_iterator wrapping iterators returning prvalues |
Yes |
3 |
|
| 979 |
NAD Editorial |
22.5.3 [move.iterators] |
Bad example |
Yes |
|
|
| 680 |
CD1 |
22.5.3.1 [move.iterator] |
move_iterator operator-> return |
Yes |
|
|
| 1211 |
Resolved |
22.5.3.1 [move.iterator] |
Move iterators should be restricted as input iterators |
Yes |
|
|
| 2576 |
C++17 |
22.6 [stream.iterators] |
istream_iterator and ostream_iterator should use std::addressof |
Yes |
0 |
|
| 1086 |
NAD Concepts |
22.6 [stream.iterators] |
Stream iterators need to be concept-constrained templates |
Yes |
|
|
| 788 |
C++11 |
22.6.1 [istream.iterator] |
Ambiguity in [istream.iterator] |
Yes |
|
|
| 838 |
C++11 |
22.6.1 [istream.iterator] |
Can an end-of-stream iterator become a non-end-of-stream one?
|
Yes |
|
|
| 245 |
NAD |
22.6.1 [istream.iterator] |
Which operations on istream_iterator trigger input operations? |
Yes |
|
|
| 2793 |
C++17 |
22.6.1.1 [istream.iterator.cons] |
Awkward conflation of trivial special members of istream_iterator |
Yes |
|
|
| 2804 |
C++17 |
22.6.1.1 [istream.iterator.cons] |
Unconditional constexpr default constructor for istream_iterator |
Yes |
0 |
|
| 2878 |
C++17 |
22.6.1.1 [istream.iterator.cons] |
Missing DefaultConstructible requirement for istream_iterator default constructor |
Yes |
|
|
| 1280 |
C++11 |
22.6.1.1 [istream.iterator.cons] |
Initialization of stream iterators |
Yes |
|
|
| 1129 |
Resolved |
22.6.1.1 [istream.iterator.cons] |
istream(buf)_iterator should support literal sentinel value |
Yes |
|
|
| 260 |
CD1 |
22.6.1.2 [istream.iterator.ops] |
Inconsistent return type of istream_iterator::operator++(int) |
Yes |
|
|
| 261 |
CD1 |
22.6.1.2 [istream.iterator.ops] |
Missing description of istream_iterator::operator!= |
Yes |
|
|
| 349 |
CD1 |
22.6.2 [ostream.iterator] |
Minor typographical error in ostream_iterator |
Yes |
|
|
| 1125 |
NAD |
22.6.2.2 [ostream.iterator.ops] |
ostream_iterator does not work with movable types |
Yes |
|
|
| 3107 |
New |
22.6.3 [istreambuf.iterator] |
istreambuf_iterator has public exposition-only member |
Yes |
4 |
|
| 2366 |
New |
22.6.3 [istreambuf.iterator] |
istreambuf_iterator end-of-stream equality |
No |
3 |
|
| 2790 |
C++17 |
22.6.3 [istreambuf.iterator] |
Missing specification of istreambuf_iterator::operator-> |
Yes |
3 |
|
| 659 |
C++11 |
22.6.3 [istreambuf.iterator] |
istreambuf_iterator should have an operator->() |
Yes |
|
|
| 110 |
TC1 |
22.6.3 [istreambuf.iterator] |
istreambuf_iterator::equal not const |
Yes |
|
|
| 3108 |
New |
22.6.3.1 [istreambuf.iterator.proxy] |
istreambuf_iterator::proxy::operator* should be const |
Yes |
3 |
|
| 2544 |
C++17 |
22.6.3.2 [istreambuf.iterator.cons] |
istreambuf_iterator(basic_streambuf<charT, traits>* s) effects unclear when s is 0 |
Yes |
3 |
|
| 1126 |
C++11 |
22.6.3.3 [istreambuf.iterator.ops] |
istreambuff_iterator::equal needs a const & parameter |
Yes |
|
|
| 39 |
TC1 |
22.6.3.3 [istreambuf.iterator.ops] |
istreambuf_iterator<>::operator++(int) definition garbled |
Yes |
|
|
| 111 |
NAD |
22.6.3.3 [istreambuf.iterator.ops] |
istreambuf_iterator::equal overspecified, inefficient |
Yes |
|
|
| 112 |
TC1 |
22.6.4.1 [ostreambuf.iter.cons] |
Minor typo in ostreambuf_iterator constructor |
Yes |
|
|
| 2457 |
New |
22.7 [iterator.range] |
std::begin() and std::end() do not support multi-dimensional arrays correctly |
No |
3 |
|
| 2812 |
C++17 |
22.7 [iterator.range] |
Range access is available with <string_view> |
Yes |
0 |
|
| 2280 |
C++14 |
22.7 [iterator.range] |
begin/end for arrays should be constexpr and noexcept |
Yes |
|
|
| 3009 |
WP |
22.8 [iterator.container] |
Including <string_view> doesn't provide std::size/empty/data |
Yes |
0 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 1282 |
Tentatively NAD |
24 [algorithms] |
A proposal to add std::split algorithm |
Yes |
|
|
| 2963 |
New |
24 [algorithms] |
Algorithms with underspecified iterator requirements |
No |
3 |
|
| 1238 |
Open |
24 [algorithms] |
Defining algorithms taking iterator for range |
No |
|
|
| 2173 |
Open |
24 [algorithms] |
The meaning of operator + in the description of the algorithms |
Yes |
4 |
|
| 1205 |
C++11 |
24 [algorithms] |
Some algorithms could more clearly document their handling of empty ranges |
Yes |
|
|
| 92 |
CD1 |
24 [algorithms] |
Incomplete Algorithm Requirements |
Yes |
|
|
| 210 |
TC1 |
24 [algorithms] |
distance first and last confused |
Yes |
|
|
| 2917 |
Resolved |
24 [algorithms] |
Parallel algorithms cannot easily work with InputIterators |
Yes |
|
|
| 1053 |
NAD |
24 [algorithms] |
Unify algorithms with operator and function object variants |
Yes |
|
|
| 631 |
NAD |
24 [algorithms] |
conflicting requirements for BinaryPredicate |
Yes |
|
|
| 2082 |
NAD |
24 [algorithms] |
Misleading complexity requirements in <algorithm> |
Yes |
|
|
| 2727 |
C++17 |
24.1 [algorithms.general] |
Parallel algorithms with constexpr specifier |
Yes |
0 |
|
| 3049 |
Open |
24.2 [algorithms.requirements] |
Missing wording allowing algorithms to use copies of function objects as substitutes for their parameters |
Yes |
3 |
|
| 2932 |
WP |
24.3.3 [algorithms.parallel.exec] |
Constraints on parallel algorithm implementations are underspecified |
Yes |
|
|
| 2718 |
C++17 |
24.3.3 [algorithms.parallel.exec] |
Parallelism bug in [algorithms.parallel.exec] p2 |
Yes |
|
|
| 2880 |
Resolved |
24.3.3 [algorithms.parallel.exec] |
Relax complexity specifications for non-sequenced policies |
Yes |
|
|
| 3062 |
WP |
24.3.5 [algorithms.parallel.overloads] |
Unnecessary decay_t in is_execution_policy_v should be remove_cvref_t |
Yes |
0 |
|
| 483 |
Dup |
24.5 [alg.nonmodifying] |
Heterogeneous equality and EqualityComparable |
Yes |
|
283 |
| 2747 |
C++17 |
24.5.4 [alg.foreach] |
Possibly redundant std::move in [alg.foreach] |
Yes |
0 |
|
| 1110 |
C++11 |
24.5.4 [alg.foreach] |
Is for_each overconstrained? |
Yes |
|
|
| 475 |
CD1 |
24.5.4 [alg.foreach] |
May the function object passed to for_each modify the elements of the iterated sequence? |
Yes |
|
|
| 969 |
NAD Editorial |
24.5.4 [alg.foreach] |
What happened to Library Issue 475? |
Yes |
|
|
| 290 |
NAD |
24.5.4 [alg.foreach] |
Requirements to for_each and its function object |
Yes |
|
|
| 219 |
NAD |
24.5.5 [alg.find] |
find algorithm missing version that takes a binary predicate argument |
Yes |
|
|
| 244 |
NAD |
24.5.5 [alg.find] |
Must find's third argument be CopyConstructible? |
Yes |
|
|
| 2150 |
C++14 |
24.5.6 [alg.find.end] |
Unclear specification of find_end |
Yes |
|
|
| 576 |
CD1 |
24.5.7 [alg.find.first.of] |
find_first_of is overconstrained |
Yes |
|
|
| 150 |
TC1 |
24.5.7 [alg.find.first.of] |
Find_first_of says integer instead of iterator |
Yes |
|
|
| 240 |
CD1 |
24.5.8 [alg.adjacent.find] |
Complexity of adjacent_find() is meaningless |
Yes |
|
|
| 1000 |
NAD Concepts |
24.5.8 [alg.adjacent.find] |
adjacent_find is over-constrained |
Yes |
|
|
| 2404 |
C++17 |
24.5.10 [mismatch] |
mismatch()'s complexity needs to be updated |
Yes |
0 |
|
| 2967 |
NAD |
24.5.11 [alg.equal] |
std::equal on empty ranges |
Yes |
|
|
| 1431 |
C++11 |
24.5.12 [alg.is_permutation] |
is_permutation must be more restrictive |
Yes |
|
|
| 1338 |
C++11 |
24.5.13 [alg.search] |
LWG 1205 incorrectly applied |
Yes |
|
|
| 426 |
CD1 |
24.5.13 [alg.search] |
search_n(), fill_n(), and generate_n() with negative n |
Yes |
|
|
| 714 |
CD1 |
24.5.13 [alg.search] |
search_n complexity is too lax |
Yes |
|
|
| 3089 |
New |
24.6.1 [alg.copy] |
copy_n should require non-overlapping ranges |
Yes |
3 |
|
| 2471 |
Open |
24.6.1 [alg.copy] |
copy_n's number of InputIterator increments unspecified |
No |
3 |
|
| 2689 |
C++17 |
24.6.1 [alg.copy] |
Parallel versions of std::copy and std::move shouldn't be in order |
Yes |
0 |
|
| 2039 |
C++14 |
24.6.1 [alg.copy] |
Issues with std::reverse and std::copy_if |
Yes |
|
|
| 2242 |
NAD |
24.6.1 [alg.copy] |
[uninitialized_]copy_n() defect |
Yes |
2 |
|
| 1206 |
C++11 |
24.6.2 [alg.move] |
Incorrect requires for move_backward and copy_backward |
Yes |
|
|
| 187 |
CD1 |
24.6.3 [alg.swap] |
iter_swap underspecified |
Yes |
|
|
| 809 |
CD1 |
24.6.3 [alg.swap] |
std::swap should be overloaded for array types |
Yes |
|
|
| 227 |
TC1 |
24.6.3 [alg.swap] |
std::swap() should require CopyConstructible or DefaultConstructible arguments |
Yes |
|
|
| 912 |
NAD Concepts |
24.6.3 [alg.swap] |
Array swap needs to be conceptualized |
Yes |
|
|
| 242 |
CD1 |
24.6.4 [alg.transform] |
Side effects of function objects |
Yes |
|
|
| 293 |
NAD |
24.6.4 [alg.transform] |
Order of execution in transform algorithm |
Yes |
|
|
| 283 |
CD1 |
24.6.5 [alg.replace] |
std::replace() requirement incorrect/insufficient |
Yes |
|
483 |
| 337 |
CD1 |
24.6.5 [alg.replace] |
replace_copy_if's template parameter should be InputIterator |
Yes |
|
|
| 913 |
NAD Concepts |
24.6.5 [alg.replace] |
Superfluous requirements for replace algorithms |
Yes |
|
|
| 1087 |
NAD Concepts |
24.6.5 [alg.replace] |
Incorrect OutputIterator concept requirements for replace algorithms |
Yes |
|
|
| 865 |
C++11 |
24.6.6 [alg.fill] |
More algorithms that throw away information |
Yes |
|
|
| 2110 |
C++14 |
24.6.8 [alg.remove] |
remove can't swap but note says it might |
Yes |
|
|
| 779 |
CD1 |
24.6.8 [alg.remove] |
Resolution of #283 incomplete |
Yes |
|
|
| 367 |
NAD |
24.6.8 [alg.remove] |
remove_copy/remove_copy_if and Input Iterators |
Yes |
|
|
| 489 |
NAD |
24.6.8 [alg.remove] |
std::remove / std::remove_if wrongly specified |
Yes |
|
|
| 2439 |
C++17 |
24.6.9 [alg.unique] |
unique_copy() sometimes can't fall back to reading its output |
Yes |
3 |
|
| 1241 |
C++11 |
24.6.9 [alg.unique] |
unique_copy needs to require EquivalenceRelation |
Yes |
|
|
| 202 |
CD1 |
24.6.9 [alg.unique] |
unique() effects unclear when predicate not an equivalence relation |
Yes |
|
|
| 239 |
CD1 |
24.6.9 [alg.unique] |
Complexity of unique() and/or unique_copy incorrect |
Yes |
|
|
| 241 |
CD1 |
24.6.9 [alg.unique] |
Does unique_copy() require CopyConstructible and Assignable? |
Yes |
|
|
| 538 |
CD1 |
24.6.9 [alg.unique] |
241 again: Does unique_copy() require CopyConstructible and Assignable? |
Yes |
|
|
| 1101 |
NAD Editorial |
24.6.9 [alg.unique] |
unique requirements |
Yes |
|
|
| 481 |
NAD |
24.6.9 [alg.unique] |
unique's effects on the range [result, last) |
Yes |
|
|
| 490 |
NAD |
24.6.9 [alg.unique] |
std::unique wrongly specified |
Yes |
|
|
| 914 |
NAD Concepts |
24.6.9 [alg.unique] |
Superfluous requirement for unique |
Yes |
|
|
| 2985 |
LEWG |
24.6.10 [alg.reverse] |
std::reverse should be permitted to be vectorized |
Yes |
|
|
| 2074 |
C++14 |
24.6.10 [alg.reverse] |
Off by one error in std::reverse_copy |
Yes |
|
|
| 223 |
TC1 |
24.6.10 [alg.reverse] |
reverse algorithm should use iter_swap rather than swap |
Yes |
|
|
| 488 |
CD1 |
24.6.11 [alg.rotate] |
rotate throws away useful information |
Yes |
|
|
| 2405 |
NAD |
24.6.11 [alg.rotate] |
rotate()'s return value is incorrect when middle == first |
Yes |
|
|
| 2716 |
C++17 |
24.6.12 [alg.random.sample] |
Specification of shuffle and sample disallows lvalue URNGs |
Yes |
0 |
|
| 1432 |
C++11 |
24.6.13 [alg.random.shuffle] |
random_shuffle signatures are inconsistent |
Yes |
|
1433 |
| 552 |
CD1 |
24.6.13 [alg.random.shuffle] |
random_shuffle and its generator |
Yes |
|
|
| 1093 |
Resolved |
24.6.13 [alg.random.shuffle] |
Multiple definitions for random_shuffle algorithm |
Yes |
|
|
| 1433 |
Dup |
24.6.13 [alg.random.shuffle] |
random_shuffle and shuffle should have consistent signatures |
Yes |
|
1432 |
| 3031 |
WP |
24.7 [alg.sorting] |
Algorithms and predicates with non-const reference arguments |
Yes |
2 |
|
| 2492 |
C++17 |
24.7 [alg.sorting] |
Clarify requirements for comp |
Yes |
0 |
|
| 556 |
C++11 |
24.7 [alg.sorting] |
Is Compare a BinaryPredicate? |
Yes |
|
|
| 218 |
NAD |
24.7 [alg.sorting] |
Algorithms do not use binary predicate objects for default comparisons |
Yes |
|
|
| 812 |
NAD Editorial |
24.7.1 [alg.sort] |
unsolicited multithreading considered harmful? |
Yes |
|
|
| 713 |
CD1 |
24.7.1.1 [sort] |
sort() complexity is too lax |
Yes |
|
|
| 499 |
NAD Editorial |
24.7.1.2 [stable.sort] |
Std. doesn't seem to require stable_sort() to be stable! |
Yes |
|
|
| 2267 |
New |
24.7.1.4 [partial.sort.copy] |
partial_sort_copy underspecified for ranges of two different types |
No |
3 |
|
| 2339 |
C++14 |
24.7.2 [alg.nth.element] |
Wording issue in nth_element |
Yes |
0 |
|
| 2163 |
C++14 |
24.7.2 [alg.nth.element] |
nth_element requires inconsistent post-conditions |
Yes |
|
|
| 270 |
CD1 |
24.7.3 [alg.binary.search] |
Binary search requirements overly strict |
Yes |
|
472 |
| 191 |
NAD |
24.7.3 [alg.binary.search] |
Unclear complexity for algorithms such as binary search |
Yes |
|
|
| 577 |
CD1 |
24.7.3.2 [upper.bound] |
upper_bound(first, last, ...) cannot return last |
Yes |
|
|
| 384 |
CD1 |
24.7.3.3 [equal.range] |
equal_range has unimplementable runtime complexity |
Yes |
|
|
| 472 |
Dup |
24.7.3.3 [equal.range] |
Missing "Returns" clause in std::equal_range |
Yes |
|
270 |
| 787 |
CD1 |
24.7.3.4 [binary.search] |
complexity of binary_search |
Yes |
|
|
| 2741 |
Open |
24.7.4 [alg.partitions] |
is_partitioned requirements need updating |
Yes |
3 |
|
| 2357 |
C++14 |
24.7.4 [alg.partitions] |
Remaining "Assignable" requirement |
Yes |
0 |
|
| 498 |
C++11 |
24.7.4 [alg.partitions] |
Requirements for partition() and stable_partition() too strong |
Yes |
|
|
| 2973 |
LEWG |
24.7.5 [alg.merge] |
inplace_merge exact comparison count complexity prohibits useful real-world optimizations |
Yes |
|
|
| 780 |
C++11 |
24.7.5 [alg.merge] |
std::merge() specification incorrect/insufficient |
Yes |
|
|
| 291 |
CD1 |
24.7.6 [alg.set.operations] |
Underspecification of set algorithms |
Yes |
|
|
| 411 |
CD1 |
24.7.6 [alg.set.operations] |
Wrong names of set member functions |
Yes |
|
|
| 3115 |
Resolved |
24.7.6.1 [includes] |
Unclear description for algorithm includes |
Yes |
3 |
|
| 862 |
NAD Editorial |
24.7.6.1 [includes] |
Impossible complexity for 'includes' |
Yes |
|
|
| 1109 |
NAD Concepts |
24.7.6.1 [includes] |
std::includes should require CopyConstructible predicate |
Yes |
|
|
| 3032 |
New |
24.7.7 [alg.heap.operations] |
ValueSwappable requirement missing for push_heap and make_heap |
Yes |
3 |
|
| 2166 |
C++17 |
24.7.7 [alg.heap.operations] |
Heap property underspecified? |
Yes |
3 |
|
| 193 |
TC1 |
24.7.7 [alg.heap.operations] |
Heap operations description incorrect |
Yes |
|
216 |
| 3029 |
Open |
24.7.7.2 [pop.heap] |
pop_heap over-constrains input |
Yes |
3 |
|
| 2444 |
WP |
24.7.7.4 [sort.heap] |
Inconsistent complexity for std::sort_heap |
Yes |
3 |
|
| 2239 |
C++17 |
24.7.8 [alg.min.max] |
min/max/minmax requirements |
Yes |
3 |
|
| 2325 |
C++17 |
24.7.8 [alg.min.max] |
minmax_element()'s behavior differing from max_element()'s should be noted |
Yes |
3 |
|
| 2369 |
C++17 |
24.7.8 [alg.min.max] |
constexpr max(initializer_list) vs max_element |
Yes |
3 |
|
| 2350 |
C++14 |
24.7.8 [alg.min.max] |
min, max, and minmax should be constexpr |
Yes |
1 |
|
| 281 |
CD1 |
24.7.8 [alg.min.max] |
std::min() and max() requirements overly restrictive |
Yes |
|
486 |
| 715 |
CD1 |
24.7.8 [alg.min.max] |
minmax_element complexity is too lax |
Yes |
|
|
| 212 |
TC1 |
24.7.8 [alg.min.max] |
Empty range behavior unclear for several algorithms |
Yes |
|
|
| 915 |
NAD Editorial |
24.7.8 [alg.min.max] |
minmax with initializer_list should return
pair of T, not pair of const T& |
Yes |
|
|
| 1013 |
NAD Editorial |
24.7.8 [alg.min.max] |
Remove IsSameType hold-over constraints |
Yes |
|
|
| 1434 |
NAD Editorial |
24.7.8 [alg.min.max] |
For min/max functions replace variadic arguments by initializer_list argument |
Yes |
|
|
| 1308 |
NAD |
24.7.8 [alg.min.max] |
Concerns about initializer_list overloads of min,
max, and minmax |
Yes |
|
|
| 190 |
NAD |
24.7.8 [alg.min.max] |
min() and max() functions should be std::binary_functions |
Yes |
|
|
| 486 |
Dup |
24.7.8 [alg.min.max] |
min/max CopyConstructible requirement is too strict |
Yes |
|
281 |
| 2688 |
C++17 |
24.7.9 [alg.clamp] |
clamp misses preconditions and has extraneous condition on result |
Yes |
0 |
|
| 142 |
TC1 |
24.7.10 [alg.lex.comparison] |
lexicographical_compare complexity wrong |
Yes |
|
|
| 3061 |
Open |
24.7.11 [alg.3way] |
What is the return type of compare_3way? |
Yes |
2 |
|
| 3169 |
New |
24.7.12 [alg.permutation.generators] |
ranges permutation generators discard useful information |
Yes |
|
|
| 2055 |
Resolved |
24.9 [numeric.ops] |
std::move in std::accumulate and other algorithms |
Yes |
3 |
|
| 2924 |
Resolved |
24.9 [numeric.ops] |
An ExecutionPolicy overload for inner_product() seems impractical |
Yes |
|
|
| 1067 |
NAD Concepts |
24.9 [numeric.ops] |
simplified wording for inner_product |
Yes |
|
|
| 2918 |
Resolved |
24.9.4 [inner.product] |
Possible need for extra storage in inner_product |
Yes |
|
|
| 3048 |
WP |
24.9.5 [transform.reduce] |
transform_reduce(exec, first1, last1, first2, init) discards execution policy |
Yes |
0 |
|
| 539 |
C++11 |
24.9.6 [partial.sum] |
partial_sum and adjacent_difference should mention requirements |
Yes |
|
|
| 3060 |
New |
24.9.7 [exclusive.scan] |
XXX_scan algorithms are specified to work with move-only T, but are
specified to make N copies of T into the destination range |
No |
|
|
| 2687 |
C++17 |
24.9.7 [exclusive.scan] |
{inclusive,exclusive}_scan misspecified |
Yes |
1 |
|
| 3058 |
WP |
24.9.11 [adjacent.difference] |
Parallel adjacent_difference shouldn't require creating temporaries |
Yes |
3 |
|
| 2919 |
Resolved |
24.9.11 [adjacent.difference] |
The specification for adjacent_difference has baked-in sequential semantics |
Yes |
|
|
| 871 |
C++11 |
24.9.12 [numeric.iota] |
Iota's requirements on T are too strong |
Yes |
|
|
| 2759 |
C++17 |
24.9.13 [numeric.ops.gcd] |
gcd / lcm and bool for the WP |
Yes |
|
|
| 2837 |
C++17 |
24.9.13 [numeric.ops.gcd] |
gcd and lcm should support a wider range of input values |
Yes |
0 |
|
| 286 |
CD1 |
24.10 [alg.c.library] |
<cstdlib> requirements missing size_t typedef |
Yes |
|
|
| 405 |
CD1 |
24.10 [alg.c.library] |
qsort and POD |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 860 |
C++11 |
25 [numerics] |
Floating-Point State |
Yes |
|
|
| 1140 |
NAD Concepts |
25 [numerics] |
Numerics library not concept enabled |
Yes |
|
|
| 3133 |
New |
25.2 [numeric.requirements] |
Modernizing numeric type requirements |
Yes |
|
|
| 2699 |
C++17 |
25.2 [numeric.requirements] |
Missing restriction in [numeric.requirements] |
Yes |
3 |
|
| 1154 |
Tentatively NAD |
25.4 [complex.numbers] |
complex should accept integral types |
Yes |
|
|
| 1217 |
Tentatively NAD |
25.4 [complex.numbers] |
Quaternion support |
No |
|
|
| 387 |
CD1 |
25.4 [complex.numbers] |
std::complex over-encapsulated |
Yes |
|
|
| 2693 |
Resolved |
25.4 [complex.numbers] |
constexpr for various std::complex arithmetic and value operators |
Yes |
3 |
|
| 388 |
NAD |
25.4 [complex.numbers] |
Use of complex as a key in associative containers |
Yes |
|
|
| 79 |
TC1 |
25.4.1 [complex.syn] |
Inconsistent declaration of polar() |
Yes |
|
|
| 80 |
TC1 |
25.4.1 [complex.syn] |
Global Operators of complex declared twice |
Yes |
|
|
| 2714 |
New |
25.4.6 [complex.ops] |
complex stream extraction underspecified |
Yes |
3 |
|
| 629 |
CD1 |
25.4.6 [complex.ops] |
complex<T> insertion and locale dependence |
Yes |
|
|
| 146 |
TC1 |
25.4.6 [complex.ops] |
complex<T> Inserter and Extractor need sentries |
Yes |
|
|
| 177 |
NAD |
25.4.6 [complex.ops] |
Complex operators cannot be explicitly instantiated |
Yes |
|
|
| 2870 |
WP |
25.4.7 [complex.value.ops] |
Default value of parameter theta of polar should be dependent |
Yes |
|
|
| 2459 |
C++17 |
25.4.7 [complex.value.ops] |
std::polar should require a non-negative rho |
Yes |
0 |
|
| 1435 |
C++11 |
25.4.7 [complex.value.ops] |
Unclear returns specifications for C99 complex number functions |
Yes |
|
|
| 595 |
CD1 |
25.4.7 [complex.value.ops] |
TR1/C++0x: fabs(complex<T>) redundant / wrongly specified |
Yes |
|
|
| 781 |
CD1 |
25.4.7 [complex.value.ops] |
std::complex should add missing C99 functions |
Yes |
|
|
| 2597 |
WP |
25.4.8 [complex.transcendentals] |
std::log misspecified for complex numbers |
Yes |
3 |
|
| 440 |
NAD |
25.4.8 [complex.transcendentals] |
Should std::complex use unqualified transcendentals? |
Yes |
|
|
| 2846 |
New |
25.4.9 [cmplx.over] |
Undefined phrase "effectively cast" |
No |
3 |
|
| 1137 |
C++11 |
25.4.9 [cmplx.over] |
Return type of conj and proj |
Yes |
|
|
| 1522 |
C++11 |
25.4.9 [cmplx.over] |
conj specification is now nonsense |
Yes |
|
|
| 844 |
CD1 |
25.4.9 [cmplx.over] |
complex pow return type is ambiguous |
Yes |
|
|
| 507 |
CD1 |
25.6 [rand] |
Missing requirement for variate_generator::operator() |
Yes |
|
|
| 699 |
CD1 |
25.6 [rand] |
N2111 changes min/max |
Yes |
|
|
| 506 |
NAD |
25.6 [rand] |
Requirements of Distribution parameter for variate_generator |
Yes |
|
|
| 547 |
NAD |
25.6 [rand] |
division should be floating-point, not integer |
Yes |
|
|
| 572 |
NAD |
25.6 [rand] |
Oops, we gave 507 WP status |
Yes |
|
|
| 1056 |
NAD |
25.6 [rand] |
Must all Engines and Distributions be Streamable? |
Yes |
|
|
| 1057 |
NAD Concepts |
25.6 [rand] |
RandomNumberEngineAdaptor |
Yes |
|
|
| 656 |
NAD Editorial |
25.6.1 [rand.synopsis] |
Typo in subtract_with_carry_engine declaration |
Yes |
|
|
| 515 |
NAD |
25.6.1 [rand.synopsis] |
Random number engine traits |
Yes |
|
|
| 505 |
CD1 |
25.6.2 [rand.req] |
Result_type in random distribution requirements |
Yes |
|
|
| 504 |
NAD Editorial |
25.6.2 [rand.req] |
Integer types in pseudo-random number engine requirements |
Yes |
|
|
| 517 |
NAD |
25.6.2 [rand.req] |
Should include name in external representation |
Yes |
|
|
| 2326 |
NAD |
25.6.2.1 [rand.req.genl] |
uniform_int_distribution<unsigned char> should be permitted |
Yes |
2 |
|
| 2181 |
C++17 |
25.6.2.2 [rand.req.seedseq] |
Exceptions from seed sequence operations |
Yes |
3 |
|
| 2124 |
NAD |
25.6.2.2 [rand.req.seedseq] |
Seed sequence over-specified |
Yes |
|
|
| 3150 |
New |
25.6.2.3 [rand.req.urng] |
UniformRandomBitGenerator should validate min and max |
Yes |
3 |
|
| 2154 |
New |
25.6.2.3 [rand.req.urng] |
What exactly does compile-time complexity imply? |
No |
4 |
|
| 2327 |
NAD |
25.6.2.3 [rand.req.urng] |
Non-power-of-two URNGs should be forbidden |
Yes |
|
|
| 654 |
CD1 |
25.6.2.4 [rand.req.eng] |
Missing IO roundtrip for random number engines |
Yes |
|
|
| 678 |
CD1 |
25.6.2.4 [rand.req.eng] |
Changes for [rand.req.eng] |
Yes |
|
|
| 729 |
NAD |
25.6.2.4 [rand.req.eng] |
Problem in [rand.req.eng]/3 |
Yes |
|
|
| 730 |
NAD |
25.6.2.5 [rand.req.adapt] |
Comment on [rand.req.adapt]/3 e) |
Yes |
|
|
| 1235 |
Tentatively NAD |
25.6.2.6 [rand.req.dist] |
Issue with C++0x random number proposal |
No |
|
|
| 733 |
NAD |
25.6.2.6 [rand.req.dist] |
Comment on [rand.req.dist]/9 |
Yes |
|
|
| 1436 |
C++11 |
25.6.3 [rand.eng] |
Random number engine constructor concerns |
Yes |
|
|
| 512 |
NAD Editorial |
25.6.3 [rand.eng] |
Seeding subtract_with_carry_01 from a single unsigned long |
Yes |
|
|
| 513 |
NAD Editorial |
25.6.3 [rand.eng] |
Size of state for subtract_with_carry_01 |
Yes |
|
|
| 516 |
NAD Editorial |
25.6.3 [rand.eng] |
Seeding subtract_with_carry_01 using a generator |
Yes |
|
|
| 2351 |
NAD |
25.6.3 [rand.eng] |
Does .seed() completely reset state of engine? |
Yes |
2 |
|
| 1437 |
C++11 |
25.6.3.2 [rand.eng.mers] |
Mersenne twister meaningless for word sizes less than two |
Yes |
|
|
| 728 |
CD1 |
25.6.3.2 [rand.eng.mers] |
Problem in [rand.eng.mers]/6 |
Yes |
|
|
| 514 |
NAD Editorial |
25.6.3.3 [rand.eng.sub] |
Size of state for subtract_with_carry |
Yes |
|
|
| 1438 |
C++11 |
25.6.4.2 [rand.adapt.disc] |
No definition for base() |
Yes |
|
|
| 738 |
NAD Editorial |
25.6.4.2 [rand.adapt.disc] |
Editorial issue in [rand.adapt.disc]/3 |
Yes |
|
|
| 609 |
CD1 |
25.6.4.3 [rand.adapt.ibits] |
missing static const |
Yes |
|
|
| 508 |
CD1 |
25.6.5 [rand.predef] |
Bad parameters for ranlux64_base_01 |
Yes |
|
|
| 796 |
NAD |
25.6.5 [rand.predef] |
ranlux48_base returns wrong value |
Yes |
|
|
| 797 |
NAD |
25.6.5 [rand.predef] |
ranlux48 returns wrong value |
Yes |
|
|
| 802 |
NAD |
25.6.5 [rand.predef] |
knuth_b returns wrong value |
Yes |
|
|
| 548 |
NAD |
25.6.6 [rand.device] |
May random_device block? |
Yes |
|
|
| 1068 |
NAD |
25.6.6 [rand.device] |
class random_device should be movable |
Yes |
|
|
| 2352 |
New |
25.6.7.1 [rand.util.seedseq] |
Is a default-constructed std::seed_seq intended to produce a predictable .generate()? |
No |
2 |
|
| 2440 |
C++17 |
25.6.7.1 [rand.util.seedseq] |
seed_seq::size() should be noexcept |
Yes |
0 |
|
| 2180 |
C++14 |
25.6.7.1 [rand.util.seedseq] |
Exceptions from std::seed_seq operations |
Yes |
|
|
| 607 |
CD1 |
25.6.7.1 [rand.util.seedseq] |
Concern about short seed vectors |
Yes |
|
|
| 608 |
CD1 |
25.6.7.1 [rand.util.seedseq] |
Unclear seed_seq construction details |
Yes |
|
|
| 677 |
CD1 |
25.6.7.1 [rand.util.seedseq] |
Weaknesses in seed_seq::randomize [rand.util.seedseq] |
Yes |
|
|
| 712 |
CD1 |
25.6.7.1 [rand.util.seedseq] |
seed_seq::size no longer useful |
Yes |
|
|
| 782 |
CD1 |
25.6.7.1 [rand.util.seedseq] |
Extended seed_seq constructor is useless |
Yes |
|
|
| 800 |
Resolved |
25.6.7.1 [rand.util.seedseq] |
Issues in 26.4.7.1 [rand.util.seedseq](6) |
Yes |
|
|
| 803 |
Resolved |
25.6.7.1 [rand.util.seedseq] |
Simplification of seed_seq::seq_seq |
Yes |
|
|
| 731 |
NAD |
25.6.7.1 [rand.util.seedseq] |
proposal for a customizable seed_seq |
Yes |
|
|
| 1069 |
NAD |
25.6.7.1 [rand.util.seedseq] |
class seed_seq should support efficient move operations |
Yes |
|
|
| 1313 |
NAD |
25.6.7.1 [rand.util.seedseq] |
Seed sequence's param function not useful for pure output iterator |
Yes |
|
|
| 655 |
CD1 |
25.6.7.2 [rand.util.canonical] |
Signature of generate_canonical not useful |
Yes |
|
|
| 739 |
NAD |
25.6.7.2 [rand.util.canonical] |
Defect in [rand.util.canonical]/3 |
Yes |
|
|
| 549 |
NAD Editorial |
25.6.8 [rand.dist] |
Undefined variable in binomial_distribution |
Yes |
|
|
| 511 |
NAD |
25.6.8 [rand.dist] |
Input_type for binomial_distribution |
Yes |
|
|
| 509 |
NAD |
25.6.8.2 [rand.dist.uni] |
Uniform_int template parameters |
Yes |
|
|
| 773 |
NAD |
25.6.8.2 [rand.dist.uni] |
issues with random |
Yes |
|
|
| 2168 |
C++17 |
25.6.8.2.2 [rand.dist.uni.real] |
Inconsistent specification of uniform_real_distribution constructor |
Yes |
3 |
|
| 510 |
NAD |
25.6.8.3 [rand.dist.bern] |
Input_type for bernoulli_distribution |
Yes |
|
|
| 735 |
NAD |
25.6.8.3.2 [rand.dist.bern.bin] |
Unfortunate naming |
Yes |
|
|
| 2406 |
C++17 |
25.6.8.3.4 [rand.dist.bern.negbin] |
negative_binomial_distribution should reject p == 1 |
Yes |
3 |
|
| 2524 |
Open |
25.6.8.4.2 [rand.dist.pois.exp] |
generate_canonical can occasionally return 1.0 |
No |
2 |
|
| 734 |
CD1 |
25.6.8.5.3 [rand.dist.norm.chisq] |
Unnecessary restriction in [rand.dist.norm.chisq] |
Yes |
|
|
| 793 |
Resolved |
25.6.8.6.1 [rand.dist.samp.discrete] |
discrete_distribution missing constructor |
Yes |
|
|
| 874 |
Resolved |
25.6.8.6.1 [rand.dist.samp.discrete] |
Missing initializer_list constructor for discrete_distribution |
Yes |
|
|
| 736 |
NAD |
25.6.8.6.1 [rand.dist.samp.discrete] |
Comment on [rand.dist.samp.discrete] |
Yes |
|
|
| 1439 |
C++11 |
25.6.8.6.2 [rand.dist.samp.pconst] |
Return from densities() functions? |
Yes |
|
|
| 792 |
CD1 |
25.6.8.6.2 [rand.dist.samp.pconst] |
piecewise_constant_distribution is undefined for a range with just one endpoint |
Yes |
|
|
| 794 |
Resolved |
25.6.8.6.2 [rand.dist.samp.pconst] |
piecewise_constant_distribution missing constructor |
Yes |
|
|
| 875 |
Resolved |
25.6.8.6.2 [rand.dist.samp.pconst] |
Missing initializer_list constructor for piecewise_constant_distribution |
Yes |
|
|
| 737 |
NAD |
25.6.8.6.2 [rand.dist.samp.pconst] |
Comment on [rand.dist.samp.pconst] |
Yes |
|
|
| 791 |
NAD |
25.6.8.6.2 [rand.dist.samp.pconst] |
piecewise_constant_distribution::densities has wrong name |
Yes |
|
|
| 1440 |
C++11 |
25.6.8.6.3 [rand.dist.samp.plinear] |
Incorrect specification for piecewise_linear_distribution |
Yes |
|
|
| 2058 |
C++14 |
25.7 [numarray] |
valarray and begin/end |
Yes |
|
|
| 621 |
CD1 |
25.7 [numarray] |
non-const copy assignment operators of helper arrays |
Yes |
|
|
| 93 |
NAD |
25.7 [numarray] |
Incomplete Valarray Subset Definitions |
Yes |
|
|
| 125 |
TC1 |
25.7.2 [template.valarray] |
valarray<T>::operator!() return type is inconsistent |
Yes |
|
|
| 107 |
NAD |
25.7.2 [template.valarray] |
Valarray constructor is strange |
Yes |
|
|
| 630 |
C++11 |
25.7.2.2 [valarray.cons] |
arrays of valarray |
Yes |
|
|
| 1208 |
C++11 |
25.7.2.2 [valarray.cons] |
valarray initializer_list constructor has incorrect effects |
Yes |
|
|
| 253 |
CD1 |
25.7.2.2 [valarray.cons] |
valarray helper functions are almost entirely useless |
Yes |
|
|
| 620 |
CD1 |
25.7.2.2 [valarray.cons] |
valid uses of empty valarrays |
Yes |
|
|
| 867 |
NAD Editorial |
25.7.2.2 [valarray.cons] |
Valarray and value-initialization |
Yes |
|
|
| 2071 |
C++14 |
25.7.2.3 [valarray.assign] |
std::valarray move-assignment |
Yes |
|
|
| 624 |
CD1 |
25.7.2.3 [valarray.assign] |
valarray assignment and arrays of unequal length |
Yes |
|
|
| 389 |
CD1 |
25.7.2.4 [valarray.access] |
Const overload of valarray::operator[] returns by value |
Yes |
|
77 |
| 636 |
NAD Editorial |
25.7.2.4 [valarray.access] |
26.5.2.3 valarray::operator[] |
Yes |
|
|
| 717 |
NAD Editorial |
25.7.2.4 [valarray.access] |
Incomplete valarray::operator[] specification in [valarray.access] |
Yes |
|
|
| 77 |
Dup |
25.7.2.4 [valarray.access] |
Valarray operator[] const returning value |
Yes |
|
389 |
| 430 |
C++11 |
25.7.2.5 [valarray.sub] |
valarray subset operations |
Yes |
|
|
| 188 |
NAD |
25.7.2.7 [valarray.cassign] |
valarray helpers missing augmented assignment operators |
Yes |
|
|
| 1243 |
NAD |
25.7.2.7 [valarray.cassign] |
Missing operator+= (initializer_list<T>) for valarray |
Yes |
|
|
| 618 |
CD1 |
25.7.2.8 [valarray.members] |
valarray::cshift() effects on empty array |
Yes |
|
|
| 3074 |
WP |
25.7.3 [valarray.nonmembers] |
Non-member functions for valarray should only deduce from the valarray |
Yes |
0 |
|
| 543 |
CD1 |
25.7.4 [class.slice] |
valarray slice default constructor |
Yes |
|
|
| 2423 |
New |
25.7.5 [template.slice.array] |
Missing specification slice_array, gslice_array, mask_array, indirect_array copy constructor |
Yes |
4 |
|
| 106 |
TC1 |
25.7.5 [template.slice.array] |
Numeric library private members are implementation defined |
Yes |
|
|
| 81 |
NAD |
25.7.5 [template.slice.array] |
Wrong declaration of slice operations |
Yes |
|
|
| 123 |
CD1 |
25.7.5.4 [slice.arr.fill] |
Should valarray helper arrays fill functions be const? |
Yes |
|
|
| 2115 |
Open |
25.7.8 [template.mask.array] |
Undefined behaviour for valarray assignments with mask_array index? |
No |
4 |
|
| 2192 |
C++17 |
25.8 [c.math] |
Validity and return type of std::abs(0u) is unclear |
Yes |
2 |
|
| 2735 |
C++17 |
25.8 [c.math] |
std::abs(short), std::abs(signed char) and others should return int instead of
double in order to be compatible with C++98 and C |
Yes |
3 |
|
| 2086 |
C++14 |
25.8 [c.math] |
Overly generic type support for math functions |
Yes |
|
|
| 1134 |
C++11 |
25.8 [c.math] |
Redundant specification of <stdint.h>, <fenv.h>, <tgmath.h>,
and maybe <complex.h> |
Yes |
|
|
| 1441 |
C++11 |
25.8 [c.math] |
Floating-point test functions are incorrectly specified |
Yes |
|
|
| 295 |
CD1 |
25.8 [c.math] |
Is abs defined in <cmath>? |
Yes |
|
|
| 395 |
CD1 |
25.8 [c.math] |
inconsistencies in the definitions of rand() and random_shuffle() |
Yes |
|
|
| 550 |
CD1 |
25.8 [c.math] |
What should the return type of pow(float,int) be? |
Yes |
|
|
| 722 |
CD1 |
25.8 [c.math] |
Missing [c.math] functions nanf and nanl |
Yes |
|
|
| 2294 |
Resolved |
25.8 [c.math] |
<cstdlib> should declare abs(double) |
Yes |
2 |
|
| 1327 |
Resolved |
25.8 [c.math] |
templates defined in <cmath> replacing C macros with the same name |
Yes |
|
|
| 357 |
NAD Editorial |
25.8 [c.math] |
<cmath> float functions cannot return HUGE_VAL |
Yes |
|
|
| 637 |
NAD Editorial |
25.8 [c.math] |
§[c.math]/10 inconsistent return values |
Yes |
|
|
| 690 |
NAD Editorial |
25.8 [c.math] |
abs(long long) should return long long |
Yes |
|
|
| 213 |
NAD |
25.8 [c.math] |
Math function overloads ambiguous |
Yes |
|
|
| 289 |
NAD |
25.8 [c.math] |
<cmath> requirements missing C float and long double versions |
Yes |
|
|
| 323 |
NAD |
25.8 [c.math] |
abs() overloads in different headers |
Yes |
|
|
| 583 |
NAD |
25.8 [c.math] |
div() for unsigned integral types |
Yes |
|
|
| 584 |
NAD |
25.8 [c.math] |
missing int pow(int,int) functionality |
Yes |
|
|
| 2079 |
NAD |
25.8 [c.math] |
Required pow() overloads |
Yes |
3 |
|
| 2474 |
NAD |
25.8 [c.math] |
<cmath> functions unfriendly to integral_constant arguments |
Yes |
4 |
|
| 2923 |
New |
25.8.1 [cmath.syn] |
noexcept is inconsistently applied across headers which import components of the C standard library |
No |
4 |
|
| 2847 |
New |
25.8.1 [cmath.syn] |
sin(float) should call sinf(float) |
No |
3 |
|
| 3051 |
WP |
25.8.1 [cmath.syn] |
Floating point classifications were inadvertently changed in P0175 |
Yes |
0 |
|
| 3093 |
New |
25.8.2 [c.math.abs] |
LWG 2294/2192 missed a std::abs overload |
No |
3 |
|
| 3066 |
New |
25.8.5 [sf.cmath] |
"report a domain error" in [sf.cmath]/1 is underspecified |
No |
3 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 708 |
Tentatively NAD |
27 [localization] |
Locales need to be per thread and updated for POSIX changes |
No |
|
|
| 317 |
CD1 |
27 [localization] |
Instantiation vs. specialization of facets |
Yes |
|
|
| 495 |
CD1 |
27 [localization] |
Clause 22 template parameter requirements |
Yes |
|
|
| 1082 |
NAD Concepts |
27 [localization] |
codecvt needs to be a concept-constrained template |
Yes |
|
|
| 1083 |
NAD Concepts |
27 [localization] |
InputIterator and OutputIterator template parameters need to be concept constraints |
Yes |
|
|
| 1298 |
C++11 |
27.2 [locale.syn] |
Missing specialization of ctype_byname<char> |
Yes |
|
|
| 268 |
CD1 |
27.3.1 [locale] |
Typo in locale synopsis |
Yes |
|
|
| 360 |
CD1 |
27.3.1 [locale] |
locale mandates inefficient implementation |
Yes |
|
|
| 31 |
TC1 |
27.3.1 [locale] |
Immutable locale values |
Yes |
|
378 |
| 37 |
TC1 |
27.3.1 [locale] |
Leftover "global" reference |
Yes |
|
|
| 137 |
TC1 |
27.3.1 [locale] |
Do use_facet and has_facet look in the global locale? |
Yes |
|
|
| 330 |
NAD |
27.3.1 [locale] |
Misleading "exposition only" value in class locale definition |
Yes |
|
|
| 378 |
Dup |
27.3.1 [locale] |
locale immutability and locale::operator=() |
Yes |
|
31 |
| 327 |
CD1 |
27.3.1.1.1 [locale.category] |
Typo in time_get facet in table 52 |
Yes |
|
447 |
| 340 |
CD1 |
27.3.1.1.1 [locale.category] |
interpretation of has_facet<Facet>(loc) |
Yes |
|
|
| 347 |
CD1 |
27.3.1.1.1 [locale.category] |
locale::category and bitmask requirements |
Yes |
|
|
| 21 |
TC1 |
27.3.1.1.1 [locale.category] |
Codecvt_byname<> instantiations |
Yes |
|
|
| 30 |
TC1 |
27.3.1.1.1 [locale.category] |
Wrong header for LC_* |
Yes |
|
|
| 121 |
NAD |
27.3.1.1.1 [locale.category] |
Detailed definition for ctype<wchar_t> specialization |
Yes |
|
|
| 502 |
NAD |
27.3.1.1.1 [locale.category] |
Proposition: Clarification of the interaction between a facet and an iterator |
Yes |
|
|
| 447 |
Dup |
27.3.1.1.1 [locale.category] |
Wrong template argument for time facets |
Yes |
|
327 |
| 2694 |
C++17 |
27.3.1.1.2 [locale.facet] |
Application of LWG 436 accidentally deleted definition of "facet" |
Yes |
3 |
|
| 436 |
CD1 |
27.3.1.1.2 [locale.facet] |
are cv-qualified facet types valid facets? |
Yes |
|
|
| 2295 |
New |
27.3.1.2 [locale.cons] |
Locale name when the provided Facet is a nullptr |
No |
3 |
|
| 2394 |
C++17 |
27.3.1.3 [locale.members] |
locale::name specification unclear — what is implementation-defined? |
Yes |
3 |
|
| 14 |
TC1 |
27.3.1.3 [locale.members] |
Locale::combine should be const |
Yes |
|
|
| 15 |
TC1 |
27.3.1.3 [locale.members] |
Locale::name requirement inconsistent |
Yes |
|
|
| 452 |
NAD |
27.3.1.3 [locale.members] |
locale::combine should be permitted to generate a named locale |
Yes |
|
|
| 8 |
TC1 |
27.3.1.5 [locale.statics] |
Locale::global lacks guarantee |
Yes |
|
|
| 38 |
TC1 |
27.3.2 [locale.global.templates] |
Facet definition incomplete |
Yes |
|
|
| 2019 |
C++11 |
27.3.3.1 [classification] |
isblank not supported by std::locale |
Yes |
|
|
| 391 |
CD1 |
27.3.3.2 [conversions] |
non-member functions specified as const |
Yes |
|
|
| 228 |
CD1 |
27.4 [locale.categories] |
Incorrect specification of "..._byname" facets |
Yes |
|
|
| 338 |
CD1 |
27.4 [locale.categories] |
is whitespace allowed between `-' and a digit? |
Yes |
|
|
| 439 |
NAD |
27.4 [locale.categories] |
Should facets be copyable? |
Yes |
|
|
| 503 |
NAD |
27.4 [locale.categories] |
more on locales |
Yes |
|
|
| 585 |
NAD |
27.4 [locale.categories] |
facet error reporting |
Yes |
|
|
| 339 |
CD1 |
27.4.1 [category.ctype] |
definition of bitmask type restricted to clause 27 |
Yes |
|
|
| 356 |
NAD |
27.4.1 [category.ctype] |
Meaning of ctype_base::mask enumerators |
Yes |
|
|
| 473 |
C++11 |
27.4.1.1 [locale.ctype] |
underspecified ctype calls |
Yes |
|
|
| 379 |
CD1 |
27.4.1.1.2 [locale.ctype.virtuals] |
nonsensical ctype::do_widen() requirement |
Yes |
|
|
| 126 |
TC1 |
27.4.1.1.2 [locale.ctype.virtuals] |
typos in Effects clause of ctype::do_narrow() |
Yes |
|
|
| 152 |
TC1 |
27.4.1.1.2 [locale.ctype.virtuals] |
Typo in scan_is() semantics |
Yes |
|
|
| 417 |
NAD |
27.4.1.1.2 [locale.ctype.virtuals] |
what does ctype::do_widen() return on failure |
Yes |
|
|
| 616 |
CD1 |
27.4.1.2 [locale.ctype.byname] |
missing 'typename' in ctype_byname |
Yes |
|
|
| 124 |
TC1 |
27.4.1.2 [locale.ctype.byname] |
ctype_byname<charT>::do_scan_is & do_scan_not return type should be const charT* |
Yes |
|
|
| 695 |
CD1 |
27.4.1.3 [facet.ctype.special] |
ctype<char>::classic_table() not accessible |
Yes |
|
|
| 153 |
CD1 |
27.4.1.3.2 [facet.ctype.char.members] |
Typo in narrow() semantics |
Yes |
|
207 |
| 28 |
TC1 |
27.4.1.3.2 [facet.ctype.char.members] |
Ctype<char>is ambiguous |
Yes |
|
236 |
| 207 |
Dup |
27.4.1.3.2 [facet.ctype.char.members] |
ctype<char> members return clause incomplete |
Yes |
|
153 |
| 236 |
Dup |
27.4.1.3.2 [facet.ctype.char.members] |
ctype<char>::is() member modifies facet |
Yes |
|
28 |
| 76 |
CD1 |
27.4.1.4 [locale.codecvt] |
Can a codecvt facet always convert one internal character at a time? |
Yes |
|
|
| 16 |
TC1 |
27.4.1.4 [locale.codecvt] |
Bad ctype_byname<char> decl |
Yes |
|
|
| 19 |
TC1 |
27.4.1.4 [locale.codecvt] |
"Noconv" definition too vague |
Yes |
|
10 |
| 24 |
TC1 |
27.4.1.4 [locale.codecvt] |
"do_convert" doesn't exist |
Yes |
|
72 |
| 33 |
TC1 |
27.4.1.4 [locale.codecvt] |
Codecvt<> mentions from_type |
Yes |
|
43 |
| 74 |
TC1 |
27.4.1.4 [locale.codecvt] |
Garbled text for codecvt::do_max_length |
Yes |
|
|
| 75 |
TC1 |
27.4.1.4 [locale.codecvt] |
Contradiction in codecvt::length's argument types |
Yes |
|
|
| 138 |
NAD |
27.4.1.4 [locale.codecvt] |
Class ctype_byname<char> redundant and misleading |
Yes |
|
|
| 382 |
NAD |
27.4.1.4 [locale.codecvt] |
codecvt do_in/out result |
Yes |
|
|
| 72 |
Dup |
27.4.1.4 [locale.codecvt] |
Do_convert phantom member function |
Yes |
|
24 |
| 664 |
CD1 |
27.4.1.4.2 [locale.codecvt.virtuals] |
do_unshift for codecvt<char, char, mbstate_t> |
Yes |
|
|
| 665 |
CD1 |
27.4.1.4.2 [locale.codecvt.virtuals] |
do_unshift return value |
Yes |
|
|
| 393 |
NAD Editorial |
27.4.1.4.2 [locale.codecvt.virtuals] |
do_in/do_out operation on state unclear |
Yes |
|
|
| 305 |
CD1 |
27.4.1.5 [locale.codecvt.byname] |
Default behavior of codecvt<wchar_t, char, mbstate_t>::length() |
Yes |
|
|
| 380 |
CD1 |
27.4.1.5 [locale.codecvt.byname] |
typos in codecvt tables 53 and 54 |
Yes |
|
|
| 381 |
CD1 |
27.4.1.5 [locale.codecvt.byname] |
detection of invalid mbstate_t in codecvt |
Yes |
|
|
| 302 |
NAD |
27.4.1.5 [locale.codecvt.byname] |
Need error indication from codecvt<>::do_length |
Yes |
|
|
| 500 |
NAD |
27.4.1.5 [locale.codecvt.byname] |
do_length cannot be implemented correctly |
Yes |
|
|
| 10 |
Dup |
27.4.1.5 [locale.codecvt.byname] |
Codecvt<>::do unclear |
Yes |
|
19 |
| 43 |
Dup |
27.4.1.5 [locale.codecvt.byname] |
Locale table correction |
Yes |
|
33 |
| 344 |
NAD |
27.4.2 [category.numeric] |
grouping + showbase |
Yes |
|
|
| 275 |
CD1 |
27.4.2.1.1 [facet.num.get.members] |
Wrong type in num_get::get() overloads |
Yes |
|
|
| 18 |
TC1 |
27.4.2.1.1 [facet.num.get.members] |
Get(...bool&) omitted |
Yes |
|
|
| 2381 |
Open |
27.4.2.1.2 [facet.num.get.virtuals] |
Inconsistency in parsing floating point numbers |
Yes |
2 |
|
| 1169 |
C++17 |
27.4.2.1.2 [facet.num.get.virtuals] |
num_get not fully compatible with strto* |
Yes |
3 |
|
| 427 |
C++11 |
27.4.2.1.2 [facet.num.get.virtuals] |
Stage 2 and rationale of DR 221 |
Yes |
|
|
| 2041 |
C++11 |
27.4.2.1.2 [facet.num.get.virtuals] |
Stage 2 accumulate incompatibilty |
Yes |
|
|
| 23 |
CD1 |
27.4.2.1.2 [facet.num.get.virtuals] |
Num_get overflow result |
Yes |
|
|
| 221 |
CD1 |
27.4.2.1.2 [facet.num.get.virtuals] |
num_get<>::do_get stage 2 processing broken |
Yes |
|
|
| 321 |
CD1 |
27.4.2.1.2 [facet.num.get.virtuals] |
Typo in num_get |
Yes |
|
|
| 358 |
CD1 |
27.4.2.1.2 [facet.num.get.virtuals] |
interpreting thousands_sep after a decimal_point |
Yes |
|
|
| 17 |
TC1 |
27.4.2.1.2 [facet.num.get.virtuals] |
Bad bool parsing |
Yes |
|
|
| 154 |
TC1 |
27.4.2.1.2 [facet.num.get.virtuals] |
Missing double specifier for do_get() |
Yes |
|
|
| 459 |
NAD |
27.4.2.1.2 [facet.num.get.virtuals] |
Requirement for widening in stage 2 is overspecification |
Yes |
|
|
| 662 |
NAD |
27.4.2.1.2 [facet.num.get.virtuals] |
Inconsistent handling of incorrectly-placed thousands separators |
Yes |
|
|
| 826 |
NAD |
27.4.2.2 [locale.nm.put] |
Equivalent of %'d, or rather, lack thereof? |
Yes |
|
|
| 359 |
CD1 |
27.4.2.2.1 [facet.num.put.members] |
num_put<>::do_put (..., bool) undocumented |
Yes |
|
|
| 2703 |
New |
27.4.2.2.2 [facet.num.put.virtuals] |
No provision for fill-padding when boolalpha is set |
No |
3 |
|
| 2702 |
New |
27.4.2.2.2 [facet.num.put.virtuals] |
num_put::do_put(..., bool) performs ill-formed do_put call |
No |
3 |
|
| 2117 |
Open |
27.4.2.2.2 [facet.num.put.virtuals] |
ios_base manipulators should have showgrouping/noshowgrouping |
No |
3 |
|
| 2293 |
C++14 |
27.4.2.2.2 [facet.num.put.virtuals] |
Wrong facet used by num_put::do_put |
Yes |
0 |
|
| 671 |
C++11 |
27.4.2.2.2 [facet.num.put.virtuals] |
precision of hexfloat |
Yes |
|
|
| 1152 |
C++11 |
27.4.2.2.2 [facet.num.put.virtuals] |
Expressions parsed differently than intended |
Yes |
|
|
| 231 |
CD1 |
27.4.2.2.2 [facet.num.put.virtuals] |
Precision in iostream? |
Yes |
|
|
| 282 |
CD1 |
27.4.2.2.2 [facet.num.put.virtuals] |
What types does numpunct grouping refer to? |
Yes |
|
|
| 34 |
TC1 |
27.4.2.2.2 [facet.num.put.virtuals] |
True/falsename() not in ctype<> |
Yes |
|
|
| 361 |
NAD |
27.4.2.2.2 [facet.num.put.virtuals] |
num_get<>::do_get (..., void*&) checks grouping |
Yes |
|
|
| 20 |
TC1 |
27.4.3.1.2 [facet.numpunct.virtuals] |
Thousands_sep returns wrong type |
Yes |
|
|
| 318 |
CD1 |
27.4.3.2 [locale.numpunct.byname] |
Misleading comment in definition of numpunct_byname |
Yes |
|
|
| 248 |
CD1 |
27.4.5 [category.time] |
time_get fails to set eofbit |
Yes |
|
|
| 71 |
TC1 |
27.4.5.1 [locale.time.get] |
Do_get_monthname synopsis missing argument |
Yes |
|
|
| 2512 |
Open |
27.4.5.1.2 [locale.time.get.virtuals] |
Y2K bites; what is an "unambiguous year identifier"? |
No |
4 |
|
| 461 |
CD1 |
27.4.5.1.2 [locale.time.get.virtuals] |
time_get hard or impossible to implement |
Yes |
|
|
| 164 |
TC1 |
27.4.5.3.2 [locale.time.put.virtuals] |
do_put() has apparently unused fill argument |
Yes |
|
|
| 836 |
C++11 |
27.4.6.1.2 [locale.money.get.virtuals] |
Effects of money_base::space and
money_base::none on money_get
|
Yes |
|
670 |
| 667 |
NAD |
27.4.6.1.2 [locale.money.get.virtuals] |
money_get's widened minus sign |
Yes |
|
|
| 668 |
NAD |
27.4.6.1.2 [locale.money.get.virtuals] |
money_get's empty minus sign |
Yes |
|
|
| 669 |
NAD |
27.4.6.1.2 [locale.money.get.virtuals] |
Equivalent postive and negative signs in money_get |
Yes |
|
|
| 2983 |
New |
27.4.6.2.2 [locale.money.put.virtuals] |
money_put::do_put underspecified |
Yes |
3 |
|
| 328 |
CD1 |
27.4.6.2.2 [locale.money.put.virtuals] |
Bad sprintf format modifier in money_put<>::do_put() |
Yes |
|
|
| 2691 |
New |
27.4.6.3 [locale.moneypunct] |
money_base::space and do_put: U+0020 versus fill |
Yes |
3 |
|
| 670 |
Dup |
27.4.6.3 [locale.moneypunct] |
money_base::pattern and space |
Yes |
|
836 |
| 374 |
NAD |
27.4.6.3.1 [locale.moneypunct.members] |
moneypunct::frac_digits returns int not unsigned |
Yes |
|
|
| 325 |
CD1 |
27.4.6.3.2 [locale.moneypunct.virtuals] |
Misleading text in moneypunct<>::do_grouping |
Yes |
|
|
| 666 |
CD1 |
27.4.6.3.2 [locale.moneypunct.virtuals] |
moneypunct::do_curr_symbol() |
Yes |
|
|
| 326 |
NAD |
27.4.6.4 [locale.moneypunct.byname] |
Missing typedef in moneypunct_byname |
Yes |
|
|
| 2028 |
C++14 |
27.4.7.1 [locale.messages] |
messages_base::catalog overspecified |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 423 |
Open |
28 [input.output] |
Effects of negative streamsize in iostreams |
Yes |
|
|
| 3130 |
WP |
28 [input.output] |
§[input.output] needs many addressof |
Yes |
0 |
|
| 44 |
CD1 |
28 [input.output] |
Iostreams use operator== on int_type values |
Yes |
|
|
| 273 |
CD1 |
28 [input.output] |
Missing ios_base qualification on members of a dependent class |
Yes |
|
|
| 308 |
CD1 |
28 [input.output] |
Table 82 mentions unrelated headers |
Yes |
|
|
| 365 |
CD1 |
28 [input.output] |
Lack of const-qualification in clause 27 |
Yes |
|
|
| 55 |
TC1 |
28 [input.output] |
Invalid stream position is undefined |
Yes |
|
|
| 366 |
NAD |
28 [input.output] |
Excessive const-qualification |
Yes |
|
|
| 1141 |
NAD Concepts |
28 [input.output] |
Input/Output library not concept enabled |
Yes |
|
|
| 623 |
CD1 |
28.2.1 [iostream.limits.imbue] |
pubimbue forbidden to call imbue |
Yes |
|
|
| 369 |
CD1 |
28.4 [iostream.objects] |
io stream objects and static ctors |
Yes |
|
|
| 455 |
CD1 |
28.4 [iostream.objects] |
cerr::tie() and wcerr::tie() are overspecified |
Yes |
|
|
| 574 |
CD1 |
28.4 [iostream.objects] |
DR 369 Contradicts Text |
Yes |
|
|
| 155 |
TC1 |
28.4 [iostream.objects] |
Typo in naming the class defining the class Init |
Yes |
|
|
| 29 |
TC1 |
28.4.3 [narrow.stream.objects] |
Ios_base::init doesn't exist |
Yes |
|
|
| 178 |
NAD |
28.4.3 [narrow.stream.objects] |
Should clog and cerr initially be tied to cout? |
Yes |
|
|
| 2087 |
C++14 |
28.5 [iostreams.base] |
iostream_category() and noexcept |
Yes |
|
|
| 1257 |
C++11 |
28.5 [iostreams.base] |
Header <ios> still contains a concept_map |
Yes |
|
|
| 35 |
TC1 |
28.5 [iostreams.base] |
No manipulator unitbuf in synopsis |
Yes |
|
|
| 2462 |
C++17 |
28.5.3 [ios.base] |
std::ios_base::failure is overspecified |
Yes |
3 |
|
| 2143 |
C++14 |
28.5.3 [ios.base] |
ios_base::xalloc should be thread-safe |
Yes |
|
|
| 41 |
TC1 |
28.5.3 [ios.base] |
Ios_base needs clear(), exceptions() |
Yes |
|
157 |
| 50 |
TC1 |
28.5.3 [ios.base] |
Copy constructor and assignment operator of ios_base |
Yes |
|
|
| 78 |
TC1 |
28.5.3 [ios.base] |
Typo: event_call_back |
Yes |
|
|
| 331 |
CD1 |
28.5.3.1.1 [ios::failure] |
bad declaration of destructor for ios_base::failure |
Yes |
|
|
| 363 |
CD1 |
28.5.3.1.1 [ios::failure] |
Missing exception specification in 27.4.2.1.1 |
Yes |
|
|
| 48 |
TC1 |
28.5.3.1.1 [ios::failure] |
Use of non-existent exception constructor |
Yes |
|
|
| 2765 |
C++17 |
28.5.3.1.6 [ios::Init] |
Did LWG 1123 go too far? |
Yes |
0 |
|
| 1123 |
C++11 |
28.5.3.1.6 [ios::Init] |
No requirement that standard streams be flushed |
Yes |
|
|
| 418 |
NAD |
28.5.3.1.6 [ios::Init] |
exceptions thrown during iostream cleanup |
Yes |
|
|
| 189 |
TC1 |
28.5.3.2 [fmtflags.state] |
setprecision() not specified correctly |
Yes |
|
|
| 287 |
NAD |
28.5.3.2 [fmtflags.state] |
conflicting ios_base fmtflags |
Yes |
|
|
| 47 |
TC1 |
28.5.3.3 [ios.base.locales] |
Imbue() and getloc() Returns clauses swapped |
Yes |
|
|
| 156 |
TC1 |
28.5.3.3 [ios.base.locales] |
Typo in imbue() description |
Yes |
|
|
| 49 |
CD1 |
28.5.3.4 [ios.members.static] |
Underspecification of ios_base::sync_with_stdio |
Yes |
|
|
| 2600 |
Tentatively NAD |
28.5.3.5 [ios.base.storage] |
ios_base must store inaccessible iostate flags |
No |
|
|
| 3083 |
WP |
28.5.3.5 [ios.base.storage] |
What should ios::iword(-1) do? |
Yes |
0 |
|
| 36 |
TC1 |
28.5.3.5 [ios.base.storage] |
Iword & pword storage lifetime omitted |
Yes |
|
|
| 157 |
Dup |
28.5.3.5 [ios.base.storage] |
Meaningless error handling for pword() and iword() |
Yes |
|
41 |
| 2675 |
New |
28.5.3.6 [ios.base.callback] |
register_callback can fail |
No |
3 |
|
| 220 |
TC1 |
28.5.3.7 [ios.base.cons] |
~ios_base() usage valid? |
Yes |
|
|
| 441 |
CD1 |
28.5.4 [fpos] |
Is fpos::state const? |
Yes |
|
|
| 6 |
NAD |
28.5.4 [fpos] |
File position not an offset unimplementable |
Yes |
|
|
| 332 |
NAD |
28.5.4 [fpos] |
Consider adding increment and decrement operators to std::fpos< T > |
Yes |
|
|
| 573 |
NAD |
28.5.4 [fpos] |
C++0x file positioning should handle modern file sizes |
Yes |
|
|
| 3118 |
New |
28.5.4.2 [fpos.operations] |
fpos equality comparison unspecified |
No |
4 |
|
| 2808 |
New |
28.5.4.2 [fpos.operations] |
Requirements for fpos and stateT |
No |
4 |
|
| 2832 |
New |
28.5.4.2 [fpos.operations] |
§[fpos.operations] strange requirement for P(i) |
No |
3 |
|
| 52 |
TC1 |
28.5.4.2 [fpos.operations] |
Small I/O problems |
Yes |
|
|
| 1444 |
Dup |
28.5.4.2 [fpos.operations] |
OFF_T is not defined |
Yes |
|
1414 |
| 194 |
NAD |
28.5.5 [ios] |
rdbuf() functions poorly specified |
Yes |
|
|
| 2214 |
Open |
28.5.5.2 [basic.ios.cons] |
Clarify basic_ios::init call restrictions |
Yes |
4 |
|
| 1249 |
C++11 |
28.5.5.2 [basic.ios.cons] |
basic_ios default ctor |
Yes |
|
|
| 53 |
TC1 |
28.5.5.2 [basic.ios.cons] |
Basic_ios destructor unspecified |
Yes |
|
|
| 145 |
NAD |
28.5.5.2 [basic.ios.cons] |
adjustfield lacks default value |
Yes |
|
|
| 835 |
C++11 |
28.5.5.3 [basic.ios.members] |
Tying two streams together (correction to DR 581) |
Yes |
|
|
| 1104 |
C++11 |
28.5.5.3 [basic.ios.members] |
basic_ios::move should accept lvalues |
Yes |
|
|
| 1183 |
C++11 |
28.5.5.3 [basic.ios.members] |
basic_ios::set_rdbuf may break class invariants |
Yes |
|
|
| 256 |
CD1 |
28.5.5.3 [basic.ios.members] |
typo in 27.4.4.2, p17: copy_event does not exist |
Yes |
|
|
| 292 |
CD1 |
28.5.5.3 [basic.ios.members] |
effects of a.copyfmt (a) |
Yes |
|
|
| 837 |
NAD Editorial |
28.5.5.3 [basic.ios.members] |
basic_ios::copyfmt() overly loosely specified
|
Yes |
|
|
| 1094 |
C++11 |
28.5.5.4 [iostate.flags] |
Replace "unspecified-bool-type" by "explicit operator bool() const" in I/O library |
Yes |
|
|
| 272 |
CD1 |
28.5.5.4 [iostate.flags] |
Missing parentheses around subexpression |
Yes |
|
569 |
| 412 |
CD1 |
28.5.5.4 [iostate.flags] |
Typo in 27.4.4.3 |
Yes |
|
429 |
| 468 |
CD1 |
28.5.5.4 [iostate.flags] |
unexpected consequences of ios_base::operator void*() |
Yes |
|
|
| 429 |
Dup |
28.5.5.4 [iostate.flags] |
typo in basic_ios::clear(iostate) |
Yes |
|
412 |
| 569 |
Dup |
28.5.5.4 [iostate.flags] |
Postcondition for basic_ios::clear(iostate) incorrectly stated |
Yes |
|
272 |
| 2504 |
New |
28.6.3 [streambuf] |
basic_streambuf is not an abstract class |
No |
3 |
|
| 56 |
TC1 |
28.6.3 [streambuf] |
Showmanyc's return type |
Yes |
|
|
| 122 |
TC1 |
28.6.3 [streambuf] |
streambuf/wstreambuf description should not say they are specializations |
Yes |
|
|
| 255 |
NAD |
28.6.3 [streambuf] |
Why do basic_streambuf<>::pbump() and gbump() take an int? |
Yes |
|
|
| 54 |
TC1 |
28.6.3.1 [streambuf.cons] |
Basic_streambuf's destructor |
Yes |
|
|
| 421 |
NAD |
28.6.3.1 [streambuf.cons] |
is basic_streambuf copy-constructible? |
Yes |
|
|
| 59 |
TC1 |
28.6.3.3.2 [streambuf.get.area] |
Ambiguity in specification of gbump |
Yes |
|
|
| 364 |
CD1 |
28.6.3.4.2 [streambuf.virt.buffer] |
Inconsistent wording in 27.5.2.4.2 |
Yes |
|
|
| 158 |
TC1 |
28.6.3.4.2 [streambuf.virt.buffer] |
Underspecified semantics for setbuf() |
Yes |
|
|
| 159 |
TC1 |
28.6.3.4.3 [streambuf.virt.get] |
Strange use of underflow() |
Yes |
|
|
| 32 |
TC1 |
28.6.3.4.4 [streambuf.virt.pback] |
Pbackfail description inconsistent |
Yes |
|
|
| 565 |
C++11 |
28.6.3.4.5 [streambuf.virt.put] |
xsputn inefficient |
Yes |
|
|
| 567 |
CD1 |
28.7 [iostream.format] |
streambuf inserter and extractor should be unformatted |
Yes |
|
|
| 1445 |
Resolved |
28.7 [iostream.format] |
Several iostreams member functions incorrectly specified |
Yes |
|
|
| 1447 |
Resolved |
28.7 [iostream.format] |
Request to resolve issue LWG 1328 |
Yes |
|
|
| 309 |
NAD |
28.7 [iostream.format] |
Does sentry catch exceptions? |
Yes |
|
|
| 1148 |
NAD |
28.7 [iostream.format] |
Wrong argument type of I/O stream manipulators setprecision()
and setw() |
Yes |
|
|
| 1446 |
NAD |
28.7 [iostream.format] |
Move and swap for I/O streams |
Yes |
|
|
| 911 |
C++11 |
28.7.4 [input.streams] |
I/O streams and move/swap semantic |
Yes |
|
|
| 160 |
TC1 |
28.7.4.1 [istream] |
Typo: Use of non-existing function exception() |
Yes |
|
|
| 113 |
NAD |
28.7.4.1 [istream] |
Missing/extra iostream sync semantics |
Yes |
|
|
| 2036 |
NAD |
28.7.4.1 [istream] |
istream >> char and eofbit |
Yes |
|
|
| 419 |
C++11 |
28.7.4.1.3 [istream::sentry] |
istream extractors not setting failbit if eofbit is already set |
Yes |
|
|
| 26 |
TC1 |
28.7.4.1.3 [istream::sentry] |
Bad sentry example |
Yes |
|
|
| 195 |
TC1 |
28.7.4.1.3 [istream::sentry] |
Should basic_istream::sentry's constructor ever set eofbit? |
Yes |
|
|
| 1328 |
Resolved |
28.7.4.1.3 [istream::sentry] |
istream extractors not setting failbit if eofbit is already set |
Yes |
|
|
| 203 |
NAD |
28.7.4.1.3 [istream::sentry] |
basic_istream::sentry::sentry() is uninstantiable with ctype<user-defined type> |
Yes |
|
|
| 2349 |
Open |
28.7.4.2.1 [istream.formatted.reqmts] |
Clarify input/output function rethrow behavior |
Yes |
3 |
|
| 373 |
CD1 |
28.7.4.2.1 [istream.formatted.reqmts] |
Are basic_istream and basic_ostream to use (exceptions()&badbit) != 0 ? |
Yes |
|
|
| 60 |
TC1 |
28.7.4.2.1 [istream.formatted.reqmts] |
What is a formatted input function? |
Yes |
|
162, 163, 166 |
| 696 |
C++11 |
28.7.4.2.2 [istream.formatted.arithmetic] |
istream::operator>>(int&) broken |
Yes |
|
|
| 118 |
CD1 |
28.7.4.2.2 [istream.formatted.arithmetic] |
basic_istream uses nonexistent num_get member functions |
Yes |
|
|
| 661 |
CD1 |
28.7.4.2.2 [istream.formatted.arithmetic] |
New 27.6.1.2.2 changes make special extractions useless |
Yes |
|
|
| 161 |
TC1 |
28.7.4.2.2 [istream.formatted.arithmetic] |
Typo: istream_iterator vs. istreambuf_iterator |
Yes |
|
|
| 413 |
CD1 |
28.7.4.2.3 [istream.extractors] |
Proposed resolution to LDR#64 still wrong |
Yes |
|
|
| 13 |
TC1 |
28.7.4.2.3 [istream.extractors] |
Eos refuses to die |
Yes |
|
|
| 64 |
TC1 |
28.7.4.2.3 [istream.extractors] |
Exception handling in basic_istream::operator>>(basic_streambuf*) |
Yes |
|
|
| 68 |
TC1 |
28.7.4.2.3 [istream.extractors] |
Extractors for char* should store null at end |
Yes |
|
|
| 2499 |
Resolved |
28.7.4.2.3 [istream.extractors] |
operator>>(basic_istream&, CharT*) makes it hard to avoid buffer overflows |
Yes |
2 |
|
| 58 |
NAD |
28.7.4.2.3 [istream.extractors] |
Extracting a char from a wide-oriented stream |
Yes |
|
|
| 639 |
NAD |
28.7.4.2.3 [istream.extractors] |
Still problems with exceptions during streambuf IO |
Yes |
|
|
| 162 |
Dup |
28.7.4.2.3 [istream.extractors] |
Really "formatted input functions"? |
Yes |
|
60 |
| 2243 |
WP |
28.7.4.3 [istream.unformatted] |
istream::putback problem |
Yes |
3 |
|
| 2244 |
C++17 |
28.7.4.3 [istream.unformatted] |
Issue on basic_istream::seekg |
Yes |
3 |
|
| 2085 |
C++14 |
28.7.4.3 [istream.unformatted] |
Wrong description of effect 1 of basic_istream::ignore |
Yes |
|
|
| 136 |
CD1 |
28.7.4.3 [istream.unformatted] |
seekp, seekg setting wrong streams? |
Yes |
|
|
| 243 |
CD1 |
28.7.4.3 [istream.unformatted] |
get and getline when sentry reports failure |
Yes |
|
|
| 370 |
CD1 |
28.7.4.3 [istream.unformatted] |
Minor error in basic_istream::get |
Yes |
|
|
| 531 |
CD1 |
28.7.4.3 [istream.unformatted] |
array forms of unformatted input functions |
Yes |
|
|
| 537 |
CD1 |
28.7.4.3 [istream.unformatted] |
Typos in the signatures in 27.6.1.3/42-43 and 27.6.2.4 |
Yes |
|
|
| 566 |
CD1 |
28.7.4.3 [istream.unformatted] |
array forms of unformatted input function undefined for zero-element arrays |
Yes |
|
|
| 61 |
TC1 |
28.7.4.3 [istream.unformatted] |
Ambiguity in iostreams exception policy |
Yes |
|
|
| 62 |
TC1 |
28.7.4.3 [istream.unformatted] |
Sync's return value |
Yes |
|
|
| 129 |
TC1 |
28.7.4.3 [istream.unformatted] |
Need error indication from seekp() and seekg() |
Yes |
|
|
| 172 |
TC1 |
28.7.4.3 [istream.unformatted] |
Inconsistent types for basic_istream::ignore() |
Yes |
|
|
| 342 |
NAD |
28.7.4.3 [istream.unformatted] |
seek and eofbit |
Yes |
|
|
| 399 |
NAD |
28.7.4.3 [istream.unformatted] |
volations of unformatted input function requirements |
Yes |
|
|
| 2131 |
NAD |
28.7.4.3 [istream.unformatted] |
Member function getline taking a string as parameter |
Yes |
|
|
| 163 |
Dup |
28.7.4.3 [istream.unformatted] |
Return of gcount() after a call to gcount |
Yes |
|
60 |
| 415 |
CD1 |
28.7.4.4 [istream.manip] |
behavior of std::ws |
Yes |
|
|
| 2498 |
New |
28.7.4.5 [istream.rvalue] |
operator>>(basic_istream&&, T&&) returns basic_istream&, but should probably return
basic_istream&& |
No |
3 |
|
| 2328 |
C++17 |
28.7.4.5 [istream.rvalue] |
Rvalue stream extraction should use perfect forwarding |
Yes |
3 |
|
| 271 |
CD1 |
28.7.4.6 [iostreamclass] |
basic_iostream missing typedefs |
Yes |
|
|
| 135 |
NAD |
28.7.4.6.1 [iostream.cons] |
basic_iostream doubly initialized |
Yes |
|
|
| 2221 |
C++17 |
28.7.5 [output.streams] |
No formatted output operator for nullptr |
Yes |
3 |
|
| 2342 |
New |
28.7.5.1 [ostream] |
User conversion to wchar_t const* or to wchar_t not invoked for operator<< |
Yes |
4 |
|
| 165 |
CD1 |
28.7.5.1 [ostream] |
xsputn(), pubsync() never called by basic_ostream members? |
Yes |
|
|
| 311 |
CD1 |
28.7.5.1 [ostream] |
Incorrect wording in basic_ostream class synopsis |
Yes |
|
|
| 2497 |
New |
28.7.5.1.3 [ostream::sentry] |
Use of uncaught_exception() |
No |
3 |
|
| 442 |
CD1 |
28.7.5.1.3 [ostream::sentry] |
sentry::operator bool() inconsistent signature |
Yes |
|
|
| 397 |
NAD Editorial |
28.7.5.1.3 [ostream::sentry] |
ostream::sentry dtor throws exceptions |
Yes |
|
|
| 398 |
NAD |
28.7.5.1.3 [ostream::sentry] |
effects of end-of-file on unformatted input functions |
Yes |
|
|
| 2341 |
C++14 |
28.7.5.1.4 [ostream.seeks] |
Inconsistency between basic_ostream::seekp(pos) and basic_ostream::seekp(off, dir) |
Yes |
0 |
|
| 394 |
NAD |
28.7.5.2.1 [ostream.formatted.reqmts] |
behavior of formatted output on failure |
Yes |
|
|
| 117 |
CD1 |
28.7.5.2.2 [ostream.inserters.arithmetic] |
basic_ostream uses nonexistent num_put member functions |
Yes |
|
|
| 640 |
CD1 |
28.7.5.2.2 [ostream.inserters.arithmetic] |
27.6.2.5.2 does not handle (unsigned) long long |
Yes |
|
|
| 437 |
NAD |
28.7.5.2.2 [ostream.inserters.arithmetic] |
Formatted output of function pointers is confusing |
Yes |
|
|
| 166 |
Dup |
28.7.5.2.3 [ostream.inserters] |
Really "formatted output functions"? |
Yes |
|
60 |
| 167 |
CD1 |
28.7.5.2.4 [ostream.inserters.character] |
Improper use of traits_type::length() |
Yes |
|
|
| 474 |
CD1 |
28.7.5.2.4 [ostream.inserters.character] |
confusing Footnote 297 |
Yes |
|
|
| 581 |
CD1 |
28.7.5.3 [ostream.unformatted] |
flush() not unformatted function |
Yes |
|
|
| 63 |
TC1 |
28.7.5.3 [ostream.unformatted] |
Exception-handling policy for unformatted output |
Yes |
|
|
| 168 |
TC1 |
28.7.5.3 [ostream.unformatted] |
Typo: formatted vs. unformatted |
Yes |
|
|
| 333 |
CD1 |
28.7.5.4 [ostream.manip] |
does endl imply synchronization with the device? |
Yes |
|
|
| 1203 |
Open |
28.7.5.5 [ostream.rvalue] |
More useful rvalue stream insertion |
Yes |
|
|
| 2534 |
C++17 |
28.7.5.5 [ostream.rvalue] |
Constrain rvalue stream operators |
Yes |
3 |
|
| 183 |
CD1 |
28.7.6 [std.manip] |
I/O stream manipulators don't work for wide character streams |
Yes |
|
|
| 216 |
Dup |
28.7.6 [std.manip] |
setbase manipulator description flawed |
Yes |
|
193 |
| 2984 |
New |
28.7.7 [ext.manip] |
put_money(99) is unnecessarily undefined |
Yes |
3 |
|
| 810 |
C++11 |
28.7.7 [ext.manip] |
Missing traits dependencies in operational semantics of extended manipulators |
Yes |
|
|
| 1299 |
C++11 |
28.7.7 [ext.manip] |
Confusing typo in specification for get_time |
Yes |
|
|
| 692 |
CD1 |
28.7.7 [ext.manip] |
get_money and put_money should be formatted I/O functions |
Yes |
|
|
| 641 |
NAD Editorial |
28.7.7 [ext.manip] |
Editorial fix for 27.6.4 (N2134) |
Yes |
|
|
| 2785 |
C++17 |
28.7.8 [quoted.manip] |
quoted should work with basic_string_view |
Yes |
0 |
|
| 2272 |
C++14 |
28.7.8 [quoted.manip] |
quoted should use char_traits::eq for character comparison |
Yes |
|
|
| 2344 |
C++14 |
28.7.8 [quoted.manip] |
quoted()'s interaction with padding is unclear |
Yes |
1 |
|
| 252 |
CD1 |
28.8 [string.streams] |
missing casts/C-style casts used in iostreams |
Yes |
|
|
| 562 |
CD1 |
28.8 [string.streams] |
stringbuf ctor inefficient |
Yes |
|
|
| 128 |
NAD |
28.8 [string.streams] |
Need open_mode() function for file stream, string streams, file buffers, and string buffers |
Yes |
|
|
| 251 |
CD1 |
28.8.2 [stringbuf] |
basic_stringbuf missing allocator_type |
Yes |
|
|
| 3006 |
New |
28.8.2.1 [stringbuf.cons] |
Constructing a basic_stringbuf from a string — where does the allocator come from? |
No |
3 |
|
| 2995 |
WP |
28.8.2.1 [stringbuf.cons] |
basic_stringbuf default constructor forbids it from using SSO capacity |
Yes |
3 |
|
| 238 |
CD1 |
28.8.2.1 [stringbuf.cons] |
Contradictory results of stringbuf initialization. |
Yes |
|
|
| 1251 |
NAD |
28.8.2.1 [stringbuf.cons] |
move constructing basic_stringbuf |
Yes |
|
|
| 1448 |
C++11 |
28.8.2.3 [stringbuf.members] |
Concerns about basic_stringbuf::str(basic_string) postconditions |
Yes |
|
|
| 3097 |
New |
28.8.2.4 [stringbuf.virtuals] |
basic_stringbuf seekoff effects trigger undefined behavior and have contradictory returns |
No |
3 |
|
| 2286 |
Open |
28.8.2.4 [stringbuf.virtuals] |
stringbuf::underflow() underspecified |
Yes |
4 |
|
| 564 |
C++11 |
28.8.2.4 [stringbuf.virtuals] |
stringbuf seekpos underspecified |
Yes |
|
|
| 375 |
CD1 |
28.8.2.4 [stringbuf.virtuals] |
basic_ios should be ios_base in 27.7.1.3 |
Yes |
|
|
| 376 |
CD1 |
28.8.2.4 [stringbuf.virtuals] |
basic_streambuf semantics |
Yes |
|
|
| 432 |
CD1 |
28.8.2.4 [stringbuf.virtuals] |
stringbuf::overflow() makes only one write position available |
Yes |
|
|
| 453 |
CD1 |
28.8.2.4 [stringbuf.virtuals] |
basic_stringbuf::seekoff need not always fail for an empty stream |
Yes |
|
|
| 563 |
CD1 |
28.8.2.4 [stringbuf.virtuals] |
stringbuf seeking from end |
Yes |
|
|
| 169 |
TC1 |
28.8.2.4 [stringbuf.virtuals] |
Bad efficiency of overflow() mandated |
Yes |
|
|
| 1449 |
C++11 |
28.8.3 [istringstream] |
Incomplete specification of header <cinttypes> |
Yes |
|
|
| 2429 |
NAD |
28.8.4 [ostringstream] |
std::basic_ostringstream is missing an allocator-extended constructor |
Yes |
|
|
| 45 |
NAD |
28.8.4 [ostringstream] |
Stringstreams read/write pointers initial position unclear |
Yes |
|
|
| 170 |
TC1 |
28.8.5 [stringstream] |
Inconsistent definition of traits_type |
Yes |
|
|
| 2121 |
NAD |
28.8.5.1 [stringstream.cons] |
app for string streams |
Yes |
3 |
|
| 2676 |
C++17 |
28.9 [file.streams] |
Provide filesystem::path overloads for File-based streams |
Yes |
2 |
|
| 420 |
CD1 |
28.9 [file.streams] |
is std::FILE a complete type? |
Yes |
|
|
| 444 |
CD1 |
28.9 [file.streams] |
Bad use of casts in fstream |
Yes |
|
|
| 460 |
CD1 |
28.9 [file.streams] |
Default modes missing from basic_fstream member specifications |
Yes |
|
|
| 73 |
NAD |
28.9 [file.streams] |
is_open should be const |
Yes |
|
|
| 863 |
NAD |
28.9 [file.streams] |
What is the state of a stream after close() succeeds |
Yes |
|
|
| 105 |
Dup |
28.9 [file.streams] |
fstream ctors argument types desired |
Yes |
|
454 |
| 643 |
CD1 |
28.9.2 [filebuf] |
Impossible "as if" clauses |
Yes |
|
|
| 2943 |
WP |
28.9.2.3 [filebuf.members] |
Problematic specification of the wide version of basic_filebuf::open |
Yes |
2 |
|
| 443 |
CD1 |
28.9.2.3 [filebuf.members] |
filebuf::close() inconsistent use of EOF |
Yes |
|
|
| 596 |
CD1 |
28.9.2.3 [filebuf.members] |
27.8.1.3 Table 112 omits "a+" and "a+b" modes |
Yes |
|
|
| 454 |
NAD |
28.9.2.3 [filebuf.members] |
basic_filebuf::open should accept wchar_t names |
Yes |
|
105 |
| 2473 |
C++17 |
28.9.2.4 [filebuf.virtuals] |
basic_filebuf's relation to C FILE semantics |
Yes |
2 |
|
| 171 |
CD1 |
28.9.2.4 [filebuf.virtuals] |
Strange seekpos() semantics due to joint position |
Yes |
|
|
| 173 |
TC1 |
28.9.2.4 [filebuf.virtuals] |
Inconsistent types for basic_filebuf::setbuf() |
Yes |
|
|
| 285 |
CD1 |
28.9.3.1 [ifstream.cons] |
minor editorial errors in fstream ctors |
Yes |
|
|
| 900 |
C++11 |
28.9.3.2 [ifstream.assign] |
Stream move-assignment |
Yes |
|
|
| 409 |
CD1 |
28.9.3.3 [ifstream.members] |
Closing an fstream should clear error state |
Yes |
|
|
| 22 |
TC1 |
28.9.3.3 [ifstream.members] |
Member open vs. flags |
Yes |
|
|
| 592 |
NAD Editorial |
28.9.3.3 [ifstream.members] |
Incorrect treatment of rdbuf()->close() return type |
Yes |
|
|
| 642 |
NAD Editorial |
28.9.3.3 [ifstream.members] |
Invalidated fstream footnotes in N2134 |
Yes |
|
|
| 1150 |
Resolved |
28.9.5 [fstream] |
wchar_t, char16_t and char32_t filenames |
Yes |
|
|
| 622 |
CD1 |
28.9.5.3 [fstream.members] |
behavior of filebuf dtor and close on error |
Yes |
|
|
| 3127 |
WP |
28.10.3.1 [syncstream.osyncstream.overview] |
basic_osyncstream::rdbuf needs a const_cast |
Yes |
0 |
|
| 2680 |
C++17 |
28.11 [filesystems] |
Add "Equivalent to" to filesystem |
Yes |
2 |
|
| 2666 |
NAD Editorial |
28.11 [filesystems] |
Bitmask operations should use bitmask terms |
Yes |
3 |
|
| 2707 |
C++17 |
28.11.7 [fs.class.path] |
path construction and assignment should have "string_type&&" overloads |
Yes |
0 |
|
| 2798 |
Resolved |
28.11.7 [fs.class.path] |
Definition of path in terms of a string |
Yes |
2 |
|
| 2668 |
NAD |
28.11.7 [fs.class.path] |
path::operator+= is defined, but not operator+ |
Yes |
3 |
|
| 2711 |
C++17 |
28.11.7.4.1 [fs.path.construct] |
path is convertible from approximately everything under the sun |
Yes |
1 |
|
| 2664 |
C++17 |
28.11.7.4.3 [fs.path.append] |
operator/ (and other append) semantics not useful if argument has root |
Yes |
2 |
|
| 2732 |
C++17 |
28.11.7.4.3 [fs.path.append] |
Questionable specification of path::operator/= and path::append |
Yes |
2 |
|
| 3055 |
New |
28.11.7.4.4 [fs.path.concat] |
path::operator+=(single-character) misspecified |
Yes |
3 |
|
| 2734 |
Resolved |
28.11.7.4.4 [fs.path.concat] |
Questionable specification in [fs.path.concat] |
Yes |
2 |
|
| 2665 |
Resolved |
28.11.7.4.5 [fs.path.modifiers] |
remove_filename() post condition is incorrect |
Yes |
1 |
|
| 2966 |
WP |
28.11.7.4.6 [fs.path.native.obs] |
Incomplete resolution of US 74 |
Yes |
|
|
| 2936 |
WP |
28.11.7.4.8 [fs.path.compare] |
Path comparison is defined in terms of the generic format |
Yes |
2 |
|
| 3098 |
New |
28.11.7.4.9 [fs.path.decompose] |
Misleading example for filesystem::path::filename() |
Yes |
3 |
|
| 2667 |
C++17 |
28.11.7.4.9 [fs.path.decompose] |
path::root_directory() description is confusing |
Yes |
0 |
|
| 3070 |
New |
28.11.7.4.11 [fs.path.gen] |
path::lexically_relative causes surprising results if a filename can also be a
root-name |
Yes |
|
|
| 3096 |
WP |
28.11.7.4.11 [fs.path.gen] |
path::lexically_relative is confused by trailing slashes |
Yes |
2 |
|
| 2674 |
C++17 |
28.11.7.5 [fs.path.itr] |
Bidirectional iterator requirement on path::iterator
is very expensive |
Yes |
2 |
|
| 2989 |
WP |
28.11.7.6 [fs.path.io] |
path's stream insertion operator lets you insert everything under the sun |
Yes |
2 |
|
| 3065 |
WP |
28.11.7.7 [fs.path.nonmember] |
LWG 2989 missed that all path's other operators should be hidden friends as well |
Yes |
2 |
|
| 3043 |
WP |
28.11.8.1 [fs.filesystem_error.members] |
Bogus postcondition for filesystem_error constructor |
Yes |
0 |
|
| 2965 |
WP |
28.11.8.1 [fs.filesystem_error.members] |
Non-existing path::native_string() in filesystem_error::what() specification |
Yes |
0 |
|
| 2947 |
New |
28.11.9.1 [fs.enum.path.format] |
Clarify several filesystem terms |
No |
3 |
|
| 2851 |
WP |
28.11.9.2 [fs.enum.file_type] |
std::filesystem enum classes are now underspecified |
Yes |
2 |
|
| 2678 |
C++17 |
28.11.9.2 [fs.enum.file_type] |
std::filesystem enum classes overspecified |
Yes |
3 |
|
| 2787 |
C++17 |
28.11.10 [fs.class.file_status] |
§[fs.file_status.cons] doesn't match class definition |
Yes |
0 |
|
| 3078 |
New |
28.11.11 [fs.class.directory_entry] |
directory_entry, directory_iterator and recursive_directory_iterator perform needless path copies |
No |
3 |
|
| 2677 |
Resolved |
28.11.11.3 [fs.dir.entry.obs] |
directory_entry::status is not allowed to be cached as a quality-of-implementation issue |
Yes |
2 |
|
| 2761 |
NAD |
28.11.11.3 [fs.dir.entry.obs] |
directory_entry comparisons are members |
Yes |
2 |
|
| 2723 |
C++17 |
28.11.12 [fs.class.directory_iterator] |
Do directory_iterator and recursive_directory_iterator become the end iterator upon error? |
Yes |
0 |
|
| 3013 |
WP |
28.11.12.1 [fs.dir.itr.members] |
(recursive_)directory_iterator construction and traversal should not be noexcept |
Yes |
0 |
|
| 2726 |
C++17 |
28.11.12.1 [fs.dir.itr.members] |
[recursive_]directory_iterator::increment(error_code&) is underspecified |
Yes |
0 |
|
| 2840 |
Resolved |
28.11.12.1 [fs.dir.itr.members] |
directory_iterator::increment is seemingly narrow-contract but marked noexcept |
Yes |
2 |
|
| 2706 |
C++17 |
28.11.13 [fs.class.rec.dir.itr] |
Error reporting for recursive_directory_iterator::pop() is under-specified |
Yes |
0 |
|
| 2708 |
Open |
28.11.13.1 [fs.rec.dir.itr.members] |
recursive_directory_iterator::recursion_pending() is incorrectly specified |
Yes |
2 |
|
| 3067 |
WP |
28.11.13.1 [fs.rec.dir.itr.members] |
recursive_directory_iterator::pop must invalidate |
Yes |
0 |
|
| 2669 |
C++17 |
28.11.13.1 [fs.rec.dir.itr.members] |
recursive_directory_iterator effects refers to non-existent functions
|
Yes |
0 |
|
| 2704 |
C++17 |
28.11.13.1 [fs.rec.dir.itr.members] |
recursive_directory_iterator's members should require '*this is dereferenceable' |
Yes |
1 |
|
| 2956 |
C++17 |
28.11.14.2 [fs.op.canonical] |
filesystem::canonical() still defined in terms of absolute(p, base) |
Yes |
1 |
|
| 3057 |
Open |
28.11.14.3 [fs.op.copy] |
Correct copy_options handling |
Yes |
2 |
|
| 2682 |
WP |
28.11.14.3 [fs.op.copy] |
filesystem::copy() won't create a symlink to a directory |
Yes |
2 |
|
| 3015 |
WP |
28.11.14.3 [fs.op.copy] |
copy_options::unspecified underspecified |
Yes |
3 |
|
| 2671 |
C++17 |
28.11.14.3 [fs.op.copy] |
Errors in Copy |
Yes |
0 |
|
| 2681 |
C++17 |
28.11.14.3 [fs.op.copy] |
filesystem::copy() cannot copy symlinks |
Yes |
2 |
|
| 2683 |
C++17 |
28.11.14.3 [fs.op.copy] |
filesystem::copy() says "no effects" |
Yes |
3 |
|
| 3056 |
New |
28.11.14.4 [fs.op.copy_file] |
copy_file() copies which attributes? |
Yes |
3 |
|
| 2849 |
WP |
28.11.14.4 [fs.op.copy_file] |
Why does !is_regular_file(from) cause copy_file to report a "file already exists" error? |
Yes |
2 |
|
| 3014 |
WP |
28.11.14.4 [fs.op.copy_file] |
More noexcept issues with filesystem operations |
Yes |
|
|
| 2712 |
C++17 |
28.11.14.4 [fs.op.copy_file] |
copy_file(from, to, ...) has a number of unspecified error conditions |
Yes |
2 |
|
| 2935 |
WP |
28.11.14.6 [fs.op.create_directories] |
What should create_directories do when p already exists but is not a directory? |
Yes |
0 |
|
| 3079 |
WP |
28.11.14.7 [fs.op.create_directory] |
LWG 2935 forgot to fix the existing_p overloads of create_directory |
Yes |
0 |
|
| 2937 |
WP |
28.11.14.12 [fs.op.equivalent] |
Is equivalent("existing_thing", "not_existing_thing") an error? |
Yes |
0 |
|
| 2722 |
C++17 |
28.11.14.12 [fs.op.equivalent] |
equivalent incorrectly specifies throws clause |
Yes |
3 |
|
| 2725 |
C++17 |
28.11.14.13 [fs.op.exists] |
filesystem::exists(const path&, error_code&) error reporting |
Yes |
1 |
|
| 2663 |
Resolved |
28.11.14.14 [fs.op.file_size] |
Enable efficient retrieval of file size from directory_entry |
Yes |
2 |
|
| 2672 |
C++17 |
28.11.14.19 [fs.op.is_empty] |
Should is_empty use error_code in its specification? |
Yes |
3 |
|
| 2719 |
C++17 |
28.11.14.26 [fs.op.permissions] |
permissions function should not be noexcept due to narrow contract |
Yes |
0 |
|
| 2720 |
C++17 |
28.11.14.26 [fs.op.permissions] |
permissions function incorrectly specified for symlinks |
Yes |
2 |
|
| 2721 |
C++17 |
28.11.14.31 [fs.op.remove_all] |
remove_all has incorrect post conditions |
Yes |
3 |
|
| 2816 |
WP |
28.11.14.33 [fs.op.resize_file] |
resize_file has impossible postcondition |
Yes |
3 |
|
| 2673 |
C++17 |
28.11.14.35 [fs.op.status] |
status() effects cannot be implemented as specified |
Yes |
0 |
|
| 2728 |
C++17 |
28.11.14.35 [fs.op.status] |
status(p).permissions() and symlink_status(p).permissions() are not specified |
Yes |
0 |
|
| 3026 |
WP |
28.11.14.39 [fs.op.weakly_canonical] |
filesystem::weakly_canonical still defined in terms of canonical(p, base) |
Yes |
0 |
|
| 984 |
C++11 |
28.12 [c.files] |
Does <cinttypes> have macro guards? |
Yes |
|
|
| 2548 |
Resolved |
28.12 [c.files] |
Missing vfscanf from <cstdio> |
Yes |
3 |
|
| 2249 |
Resolved |
28.12 [c.files] |
[CD] Remove gets from <cstdio> |
Yes |
|
|
| 2043 |
NAD |
28.12 [c.files] |
std{in,out,err} should be usable as field names |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 1089 |
C++11 |
31 [thread] |
Unify "Throws: Nothing." specifications |
Yes |
|
|
| 1442 |
NAD Editorial |
31 [thread] |
"happens-before" should be "synchronizes-with" |
Yes |
|
1443 |
| 1443 |
Dup |
31 [thread] |
Imposed happens-before edges are not made transitive |
Yes |
|
1442 |
| 1139 |
NAD Concepts |
31 [thread] |
Thread support library not concept enabled |
Yes |
|
|
| 1481 |
Resolved |
31.2 [thread.req] |
Missing Lockable requirements |
Yes |
|
|
| 1108 |
C++11 |
31.2.2 [thread.req.exception] |
thread.req.exception overly constrains implementations |
Yes |
|
|
| 2379 |
NAD |
31.2.3 [thread.req.native] |
Obtaining native handle of the current thread |
Yes |
|
|
| 2941 |
WP |
31.2.4 [thread.req.timing] |
§[thread.req.timing] wording should apply to both member and namespace-level functions |
Yes |
0 |
|
| 1158 |
C++11 |
31.2.4 [thread.req.timing] |
Encouragement to use monotonic clock |
Yes |
|
|
| 1482 |
Resolved |
31.2.4 [thread.req.timing] |
Timeout operations are under-specified |
Yes |
|
|
| 2819 |
New |
31.2.5 [thread.req.lockable] |
Unspecified Return type: elements |
No |
3 |
|
| 2999 |
New |
31.2.6 [thread.decaycopy] |
§[thread.decaycopy] issue |
No |
3 |
|
| 1483 |
NAD Editorial |
31.3 [thread.threads] |
__STDCPP_THREADS spelling |
Yes |
|
|
| 1484 |
LEWG |
31.3.2 [thread.thread.class] |
Need a way to join a thread with a timeout |
No |
|
|
| 1277 |
C++11 |
31.3.2.1 [thread.thread.id] |
std::thread::id should be trivially copyable |
Yes |
|
|
| 783 |
CD1 |
31.3.2.1 [thread.thread.id] |
thread::id reuse |
Yes |
|
|
| 889 |
Resolved |
31.3.2.1 [thread.thread.id] |
thread::id comparisons |
Yes |
|
|
| 1485 |
NAD |
31.3.2.1 [thread.thread.id] |
Unclear thread::id specification |
Yes |
|
|
| 3039 |
WP |
31.3.2.2 [thread.thread.constr] |
Unnecessary decay in thread and packaged_task |
Yes |
0 |
|
| 891 |
C++11 |
31.3.2.2 [thread.thread.constr] |
std::thread, std::call_once issue |
Yes |
|
|
| 929 |
C++11 |
31.3.2.2 [thread.thread.constr] |
Thread constructor |
Yes |
|
|
| 967 |
C++11 |
31.3.2.2 [thread.thread.constr] |
Various threading bugs #17 |
Yes |
|
|
| 1176 |
NAD |
31.3.2.2 [thread.thread.constr] |
Make thread constructor non-variadic |
Yes |
|
|
| 963 |
C++11 |
31.3.2.5 [thread.thread.member] |
Various threading bugs #13 |
Yes |
|
|
| 1033 |
C++11 |
31.3.2.5 [thread.thread.member] |
thread::join() effects? |
Yes |
|
|
| 888 |
C++11 |
31.3.3 [thread.thread.this] |
this_thread::yield too strong |
Yes |
|
|
| 1487 |
C++11 |
31.3.3 [thread.thread.this] |
Clock related operations exception specifications conflict |
Yes |
|
|
| 1486 |
NAD |
31.3.3 [thread.thread.this] |
Value of this_thread::get_id() underspecified for detached thread |
Yes |
|
|
| 1488 |
LEWG |
31.4 [thread.mutex] |
Improve interoperability between the C++0x and C1x threads APIs |
No |
|
|
| 1044 |
C++11 |
31.4 [thread.mutex] |
Empty tag types should be constexpr literals |
Yes |
|
|
| 1268 |
Resolved |
31.4 [thread.mutex] |
The Mutex requirements in 30.4.1 and 30.4.2 are wrong |
Yes |
|
|
| 1489 |
NAD Editorial |
31.4 [thread.mutex] |
unlock functions and unlock mutex requirements are inconsistent |
Yes |
|
|
| 936 |
LEWG |
31.4.3 [thread.mutex.requirements] |
Mutex type overspecified |
No |
|
961 |
| 961 |
LEWG |
31.4.3 [thread.mutex.requirements] |
Various threading bugs #11 |
No |
|
936 |
| 1493 |
LEWG |
31.4.3 [thread.mutex.requirements] |
Add mutex, recursive_mutex, is_locked function |
No |
|
|
| 2126 |
Pending NAD Editorial |
31.4.3 [thread.mutex.requirements] |
Several specification problems in regard to mutex requirements |
Yes |
|
|
| 960 |
C++11 |
31.4.3 [thread.mutex.requirements] |
Various threading bugs #10 |
Yes |
|
|
| 968 |
C++11 |
31.4.3 [thread.mutex.requirements] |
Various threading bugs #18 |
Yes |
|
|
| 1218 |
C++11 |
31.4.3 [thread.mutex.requirements] |
mutex destructor synchronization |
Yes |
|
|
| 1490 |
Resolved |
31.4.3 [thread.mutex.requirements] |
Mutex requirements too stringent |
Yes |
|
|
| 1491 |
Resolved |
31.4.3 [thread.mutex.requirements] |
try_lock does not guarantee forward progress |
Yes |
|
|
| 1492 |
Resolved |
31.4.3 [thread.mutex.requirements] |
Mutex requirements should not be bound to threads |
Yes |
|
|
| 980 |
NAD |
31.4.3 [thread.mutex.requirements] |
mutex lock() missing error conditions |
Yes |
|
|
| 2134 |
Pending NAD Editorial |
31.4.3.2 [thread.mutex.requirements.mutex] |
Redundant Mutex requirement? |
Yes |
|
|
| 2309 |
C++17 |
31.4.3.2 [thread.mutex.requirements.mutex] |
mutex::lock() should not throw device_or_resource_busy |
Yes |
0 |
|
| 2090 |
NAD |
31.4.3.2 [thread.mutex.requirements.mutex] |
Minor Overconstraint in Mutex Types |
Yes |
|
|
| 893 |
C++11 |
31.4.3.2.1 [thread.mutex.class] |
std::mutex issue |
Yes |
|
905 |
| 828 |
Resolved |
31.4.3.2.1 [thread.mutex.class] |
Static initialization for std::mutex? |
Yes |
|
|
| 905 |
Dup |
31.4.3.2.1 [thread.mutex.class] |
Mutex specification questions |
Yes |
|
893 |
| 2125 |
Pending NAD Editorial |
31.4.3.3 [thread.timedmutex.requirements] |
TimedMutex specification problem |
Yes |
|
|
| 2091 |
C++14 |
31.4.3.3 [thread.timedmutex.requirements] |
Misplaced effect in m.try_lock_for() |
Yes |
|
|
| 2288 |
C++14 |
31.4.3.4 [thread.sharedmutex.requirements] |
Inconsistent requirements for shared mutexes |
Yes |
|
|
| 2363 |
Open |
31.4.3.5.1 [thread.sharedtimedmutex.class] |
Defect in 30.4.1.4.1 [thread.sharedtimedmutex.class] |
Yes |
2 |
|
| 2731 |
Open |
31.4.4.1 [thread.lock.guard] |
Existence of lock_guard<MutexTypes...>::mutex_type typedef unclear |
Yes |
3 |
|
| 2887 |
Resolved |
31.4.4.1 [thread.lock.guard] |
Revert the changes from P0156R0: variadic lock_guard |
Yes |
|
|
| 2023 |
Resolved |
31.4.4.1 [thread.lock.guard] |
Incorrect requirements for lock_guard and unique_lock |
Yes |
|
|
| 2104 |
C++14 |
31.4.4.3 [thread.lock.unique] |
unique_lock move-assignment should not be noexcept |
Yes |
|
|
| 2577 |
C++17 |
31.4.4.3.1 [thread.lock.unique.cons] |
{shared,unique}_lock should use std::addressof |
Yes |
0 |
|
| 1045 |
C++11 |
31.4.4.3.1 [thread.lock.unique.cons] |
Remove unnecessary preconditions from unique_lock constructor |
Yes |
|
|
| 962 |
C++11 |
31.4.4.3.2 [thread.lock.unique.locking] |
Various threading bugs #12 |
Yes |
|
|
| 1159 |
C++11 |
31.4.4.3.2 [thread.lock.unique.locking] |
Unclear spec for resource_deadlock_would_occur |
Yes |
|
1219 |
| 1219 |
Dup |
31.4.4.3.2 [thread.lock.unique.locking] |
unique_lock::lock and resource_deadlock_would_occur |
Yes |
|
1159 |
| 784 |
NAD |
31.4.4.3.3 [thread.lock.unique.mod] |
unique_lock::release |
Yes |
|
|
| 3030 |
WP |
31.4.5 [thread.lock.algorithm] |
Who shall meet the requirements of try_lock? |
Yes |
0 |
|
| 986 |
C++11 |
31.4.5 [thread.lock.algorithm] |
Generic try_lock contradiction |
Yes |
|
|
| 2080 |
C++14 |
31.4.6 [thread.once] |
Specify when once_flag becomes invalid |
Yes |
|
|
| 2442 |
C++17 |
31.4.6.2 [thread.once.callonce] |
call_once() shouldn't DECAY_COPY() |
Yes |
|
|
| 1494 |
C++11 |
31.4.6.2 [thread.once.callonce] |
Term "are serialized" not defined |
Yes |
|
|
| 1499 |
Tentatively NAD |
31.5 [thread.condition] |
Condition variables preclude wakeup optimization |
No |
|
|
| 2140 |
C++14 |
31.5 [thread.condition] |
Meaning of notify_all_at_thread_exit synchronization requirement? |
Yes |
|
|
| 2190 |
C++14 |
31.5 [thread.condition] |
Condition variable specification |
Yes |
|
|
| 859 |
C++11 |
31.5 [thread.condition] |
Monotonic Clock is Conditionally Supported? |
Yes |
|
|
| 1220 |
C++11 |
31.5 [thread.condition] |
What does condition_variable wait on? |
Yes |
|
|
| 1222 |
C++11 |
31.5 [thread.condition] |
condition_variable incorrect effects for exception safety |
Yes |
|
|
| 1497 |
C++11 |
31.5 [thread.condition] |
lock() postcondition can not be generally achieved |
Yes |
|
|
| 1498 |
Resolved |
31.5 [thread.condition] |
Unclear specification for [thread.condition] |
Yes |
|
|
| 1495 |
NAD Editorial |
31.5 [thread.condition] |
Condition variable wait_for return value insufficient |
Yes |
|
|
| 2093 |
C++14 |
31.5.3 [thread.condition.condvar] |
Throws clause of condition_variable::wait with predicate |
Yes |
|
|
| 2135 |
C++14 |
31.5.3 [thread.condition.condvar] |
Unclear requirement for exceptions thrown in condition_variable::wait() |
Yes |
|
|
| 857 |
C++11 |
31.5.3 [thread.condition.condvar] |
condition_variable::time_wait return bool error prone |
Yes |
|
|
| 965 |
C++11 |
31.5.3 [thread.condition.condvar] |
Various threading bugs #15 |
Yes |
|
|
| 1221 |
C++11 |
31.5.3 [thread.condition.condvar] |
condition_variable wording |
Yes |
|
|
| 958 |
Resolved |
31.5.3 [thread.condition.condvar] |
Various threading bugs #8 |
Yes |
|
|
| 966 |
Resolved |
31.5.3 [thread.condition.condvar] |
Various threading bugs #16 |
Yes |
|
|
| 2240 |
Resolved |
31.5.3 [thread.condition.condvar] |
Probable misuse of term "function scope" in [thread.condition] |
Yes |
|
|
| 1496 |
NAD Editorial |
31.5.3 [thread.condition.condvar] |
condition_variable not implementable |
Yes |
|
|
| 887 |
NAD |
31.5.3 [thread.condition.condvar] |
issue with condition::wait_... |
Yes |
|
|
| 959 |
NAD |
31.5.3 [thread.condition.condvar] |
Various threading bugs #9 |
Yes |
|
|
| 2092 |
C++14 |
31.5.4 [thread.condition.condvarany] |
Vague Wording for condition_variable_any |
Yes |
|
|
| 1267 |
C++11 |
31.5.4 [thread.condition.condvarany] |
Incorrect wording for condition_variable_any::wait_for |
Yes |
|
|
| 964 |
Resolved |
31.5.4 [thread.condition.condvarany] |
Various threading bugs #14 |
Yes |
|
|
| 1500 |
NAD Editorial |
31.5.4 [thread.condition.condvarany] |
Consider removal of native_handle() |
Yes |
|
|
| 1223 |
NAD |
31.5.4 [thread.condition.condvarany] |
condition_variable_any lock matching? |
Yes |
|
|
| 1224 |
NAD |
31.5.4 [thread.condition.condvarany] |
condition_variable_any support for recursive mutexes? |
Yes |
|
|
| 2276 |
C++17 |
31.6 [futures] |
Missing requirement on std::promise::set_exception |
Yes |
|
|
| 1518 |
C++11 |
31.6 [futures] |
Waiting for deferred functions |
Yes |
|
|
| 1046 |
Resolved |
31.6 [futures] |
Provide simple facility to start asynchronous operations |
Yes |
|
|
| 1244 |
Resolved |
31.6 [futures] |
wait_*() in *future for synchronous functions |
Yes |
|
|
| 1275 |
Resolved |
31.6 [futures] |
Creating and setting futures |
Yes |
|
|
| 1501 |
Resolved |
31.6 [futures] |
Specification for managing associated asynchronous state has problems |
Yes |
|
|
| 1513 |
Resolved |
31.6 [futures] |
'launch' enum too restrictive |
Yes |
|
|
| 2056 |
C++14 |
31.6.1 [futures.overview] |
future_errc enums start with value 0 (invalid value for broken_promise) |
Yes |
|
|
| 2102 |
C++14 |
31.6.1 [futures.overview] |
Why is std::launch an implementation-defined type? |
Yes |
|
|
| 1226 |
Resolved |
31.6.3 [futures.errors] |
Incomplete changes of #890 |
Yes |
|
|
| 1160 |
Resolved |
31.6.4 [futures.future_error] |
future_error public constructor is 'exposition only' |
Yes |
|
|
| 2530 |
Open |
31.6.5 [futures.state] |
Clarify observable side effects of releasing a shared state |
No |
3 |
|
| 1269 |
Resolved |
31.6.5 [futures.state] |
Associated state doesn't account for async |
Yes |
|
|
| 1502 |
Resolved |
31.6.5 [futures.state] |
Specification of [futures.state] unclear |
Yes |
|
|
| 1503 |
NAD Editorial |
31.6.5 [futures.state] |
"associated asynchronous state" must go |
Yes |
|
|
| 3003 |
Open |
31.6.6 [futures.promise] |
<future> still has type-erased allocators in promise |
Yes |
2 |
|
| 2532 |
Open |
31.6.6 [futures.promise] |
Satisfying a promise at thread exit |
Yes |
3 |
|
| 2095 |
LEWG |
31.6.6 [futures.promise] |
promise and packaged_task missing constructors needed for uses-allocator construction |
Yes |
4 |
|
| 2412 |
WP |
31.6.6 [futures.promise] |
promise::set_value() and promise::get_future() should not race |
Yes |
3 |
|
| 2523 |
C++17 |
31.6.6 [futures.promise] |
std::promise synopsis shows two set_value_at_thread_exit()'s for no apparent reason |
Yes |
0 |
|
| 2098 |
C++14 |
31.6.6 [futures.promise] |
Minor Inconsistency between promise::set_value and promise::set_value_at_thread_exit |
Yes |
|
|
| 1049 |
Resolved |
31.6.6 [futures.promise] |
Move assignment of promise inverted |
Yes |
|
|
| 1050 |
Resolved |
31.6.6 [futures.promise] |
Clarify postconditions for get_future() |
Yes |
|
|
| 1088 |
Resolved |
31.6.6 [futures.promise] |
std::promise should provide non-member swap overload |
Yes |
|
|
| 1165 |
Resolved |
31.6.6 [futures.promise] |
Unneeded promise move constructor |
Yes |
|
|
| 1272 |
Resolved |
31.6.6 [futures.promise] |
confusing declarations of promise::set_value |
Yes |
|
|
| 1291 |
Resolved |
31.6.6 [futures.promise] |
Exceptions thrown during promise::set_value |
Yes |
|
|
| 1300 |
Resolved |
31.6.6 [futures.promise] |
Circular definition of promise::swap |
Yes |
|
|
| 1504 |
Resolved |
31.6.6 [futures.promise] |
Term "are serialized" is not defined |
Yes |
|
|
| 1505 |
Resolved |
31.6.6 [futures.promise] |
Synchronization between promise::set_value and future::get |
Yes |
|
|
| 1507 |
Resolved |
31.6.6 [futures.promise] |
promise::XXX_at_thread_exit functions have no
synchronization requirements |
Yes |
|
|
| 1506 |
NAD Editorial |
31.6.6 [futures.promise] |
set_exception with a null pointer |
Yes |
|
|
| 1164 |
NAD |
31.6.6 [futures.promise] |
promise::swap should pass by rvalue reference |
Yes |
|
|
| 2531 |
C++17 |
31.6.7 [futures.unique_future] |
future::get should explicitly state that the shared state is released |
Yes |
3 |
|
| 2556 |
C++17 |
31.6.7 [futures.unique_future] |
Wide contract for future::share() |
Yes |
3 |
|
| 2096 |
C++14 |
31.6.7 [futures.unique_future] |
Incorrect constraints of future::get in regard to MoveAssignable |
Yes |
|
|
| 2185 |
C++14 |
31.6.7 [futures.unique_future] |
Missing throws clause for future/shared_future::wait_for/wait_until |
Yes |
|
|
| 2031 |
C++11 |
31.6.7 [futures.unique_future] |
std::future<>::share() only applies to rvalues |
Yes |
|
|
| 1047 |
Resolved |
31.6.7 [futures.unique_future] |
Ensure that future's get() blocks when not ready |
Yes |
|
|
| 1048 |
Resolved |
31.6.7 [futures.unique_future] |
Provide empty-state inspection for std::unique_future |
Yes |
|
|
| 1161 |
Resolved |
31.6.7 [futures.unique_future] |
Unnecessary unique_future limitations |
Yes |
|
|
| 1273 |
Resolved |
31.6.7 [futures.unique_future] |
future::valid should be callable on an invalid future |
Yes |
|
|
| 2799 |
Resolved |
31.6.8 [futures.shared_future] |
noexcept-specifications in shared_future |
Yes |
2 |
|
| 2920 |
Resolved |
31.6.8 [futures.shared_future] |
Add a deduction guide for creating a shared_future from a future rvalue |
Yes |
|
|
| 1106 |
Resolved |
31.6.8 [futures.shared_future] |
Multiple exceptions from connected shared_future::get()? |
Yes |
|
|
| 1162 |
Resolved |
31.6.8 [futures.shared_future] |
shared_future should support an efficient move constructor |
Yes |
|
|
| 1163 |
Resolved |
31.6.8 [futures.shared_future] |
shared_future is inconsistent with shared_ptr |
Yes |
|
|
| 1266 |
Resolved |
31.6.8 [futures.shared_future] |
shared_future::get and deferred async functions |
Yes |
|
|
| 1304 |
Resolved |
31.6.8 [futures.shared_future] |
Missing preconditions for shared_future |
Yes |
|
|
| 1107 |
NAD Editorial |
31.6.8 [futures.shared_future] |
constructor shared_future(unique_future) by value? |
Yes |
|
|
| 2046 |
NAD |
31.6.8 [futures.shared_future] |
shared_future(future<R>&&) should be allowed to throw |
Yes |
|
|
| 2202 |
Deferred |
31.6.9 [futures.async] |
Missing allocator support by async |
No |
4 |
|
| 2752 |
C++17 |
31.6.9 [futures.async] |
"Throws:" clauses of async and packaged_task are unimplementable |
Yes |
3 |
|
| 2186 |
C++14 |
31.6.9 [futures.async] |
Incomplete action on async/launch::deferred |
Yes |
|
|
| 2078 |
C++14 |
31.6.9 [futures.async] |
Throw specification of async() incomplete |
Yes |
|
|
| 2100 |
C++14 |
31.6.9 [futures.async] |
timed waiting functions cannot timeout if launch::async policy used |
Yes |
|
|
| 2120 |
C++14 |
31.6.9 [futures.async] |
What should async do if neither 'async' nor 'deferred' is set in policy? |
Yes |
|
|
| 2032 |
C++11 |
31.6.9 [futures.async] |
Incorrect synchronization clause of async function |
Yes |
|
|
| 2856 |
Resolved |
31.6.9 [futures.async] |
std::async should be marked as [[nodiscard]] |
Yes |
2 |
|
| 1315 |
NAD Editorial |
31.6.9 [futures.async] |
return type of async |
Yes |
|
|
| 1512 |
NAD Editorial |
31.6.9 [futures.async] |
Conflict in specification: block or join? |
Yes |
|
|
| 3117 |
New |
31.6.10 [futures.task] |
Missing packaged_task deduction guides |
Yes |
3 |
|
| 2976 |
WP |
31.6.10 [futures.task] |
Dangling uses_allocator specialization for packaged_task |
Yes |
3 |
|
| 2921 |
C++17 |
31.6.10 [futures.task] |
packaged_task and type-erased allocators |
Yes |
|
|
| 2067 |
C++14 |
31.6.10 [futures.task] |
packaged_task should have deleted copy c'tor with const parameter |
Yes |
|
|
| 2030 |
C++11 |
31.6.10 [futures.task] |
packaged_task::result_type should be removed |
Yes |
|
|
| 1090 |
Resolved |
31.6.10 [futures.task] |
Missing description of packaged_task member swap, missing non-member swap |
Yes |
|
|
| 1508 |
Resolved |
31.6.10 [futures.task] |
Rename packaged_task::operator bool() |
Yes |
|
|
| 2407 |
C++17 |
31.6.10.1 [futures.task.members] |
packaged_task(allocator_arg_t, const Allocator&, F&&) should neither be constrained nor
explicit |
Yes |
|
|
| 2097 |
C++14 |
31.6.10.1 [futures.task.members] |
packaged_task constructors should be constrained |
Yes |
|
|
| 2142 |
C++14 |
31.6.10.1 [futures.task.members] |
packaged_task::operator() synchronization too broad? |
Yes |
|
|
| 1514 |
C++11 |
31.6.10.1 [futures.task.members] |
packaged_task constructors need review |
Yes |
|
|
| 2008 |
C++11 |
31.6.10.1 [futures.task.members] |
Conflicting Error Conditions for packaged_task::operator() |
Yes |
|
|
| 2027 |
C++11 |
31.6.10.1 [futures.task.members] |
Initialization of the stored task of a packaged_task |
Yes |
|
|
| 2245 |
Resolved |
31.6.10.1 [futures.task.members] |
packaged_task::reset() memory allocation |
Yes |
3 |
|
| 1515 |
Resolved |
31.6.10.1 [futures.task.members] |
packaged_task::make_ready_at_thread_exit has no synchronization requirements |
Yes |
|
|
| 2025 |
Resolved |
31.6.10.1 [futures.task.members] |
Incorrect semantics of move assignment operator of packaged_task |
Yes |
|
|
| 2000 |
C++11 |
31.6.10.2 [futures.task.nonmembers] |
Missing definition of packaged_task specialization of uses_allocator |
Yes |
|
|