| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 3105 |
New |
16 [library] |
T1 is convertible to T2 |
No |
3 |
|
| 2949 |
New |
16 [library] |
Unclear complexity requirements: space vs. time |
No |
4 |
|
| 2392 |
New |
16.3.18 [defns.ntcts] |
"character type" is used but not defined |
No |
3 |
|
| 2136 |
Open |
16.4.1 [structure] |
Postconditions vs. exceptions |
No |
3 |
|
| 3193 |
New |
16.4.1.4 [structure.specifications] |
Mandates: and Expects: elements are not defined for types |
Yes |
3 |
|
| 3168 |
Open |
16.4.1.4 [structure.specifications] |
Expects: element should be specified in one place |
Yes |
2 |
|
| 2292 |
Tentatively Resolved |
16.4.1.4 [structure.specifications] |
Find a better phrasing for "shall not participate in overload resolution" |
No |
3 |
|
| 2999 |
Tentatively Resolved |
16.4.2.1 [expos.only.func] |
§[thread.decaycopy] issue |
No |
3 |
|
| 3092 |
Open |
16.4.2.2.4 [bitmask.types] |
Unclear semantics of enum class bitmask types |
Yes |
3 |
|
| 3285 |
Voting |
16.4.2.2.6 [customization.point.object] |
The type of a customization point object shall satisfy semiregular |
Yes |
0 |
|
| 2818 |
Open |
16.5.1.1 [contents] |
"::std::" everywhere rule needs tweaking |
No |
2 |
|
| 3240 |
New |
16.5.2.2 [using.headers] |
Headers declare more than entities |
No |
|
|
| 2146 |
Open |
16.5.3.1 [utility.arg.requirements] |
Are reference types Copy/Move-Constructible/Assignable or Destructible? |
No |
2 |
|
| 2152 |
LEWG |
16.5.3.2 [swappable.requirements] |
Instances of standard container types are not swappable |
Yes |
3 |
|
| 2114 |
Open |
16.5.3.3 [nullablepointer.requirements] |
Incorrect "contextually convertible to bool" requirements |
Yes |
3 |
|
| 3315 |
Voting |
16.5.3.5 [allocator.requirements] |
Correct Allocator Default Behavior |
Yes |
0 |
|
| 3267 |
New |
16.5.3.5 [allocator.requirements] |
Rebound allocators and is_always_equal |
Yes |
4 |
|
| 3157 |
New |
16.5.3.5 [allocator.requirements] |
Allocator destroy and fancy pointer operations must be non-throwing |
Yes |
3 |
|
| 3044 |
New |
16.5.3.5 [allocator.requirements] |
Strange specification of max_size() for an allocator |
Yes |
3 |
|
| 2461 |
New |
16.5.3.5 [allocator.requirements] |
Interaction between allocators and container exception safety guarantees |
No |
3 |
|
| 3177 |
New |
16.5.4.2.1 [namespace.std] |
Limit permission to specialize variable templates to program-defined types |
Yes |
3 |
|
| 3142 |
New |
16.5.4.8 [res.on.functions] |
std::foo<incomplete> should be ill-formed NDR |
Yes |
3 |
|
| 2695 |
New |
16.5.5.5 [member.functions] |
"As if" unclear in [member.functions] |
No |
3 |
|
| 2414 |
Open |
16.5.5.9 [reentrancy] |
Member function reentrancy should be implementation-defined |
Yes |
3 |
|
| 3229 |
New |
16.5.5.13 [res.on.exception.handling] |
§[res.on.exception.handling]#3 cannot apply to types with implicitly declared destructors |
Yes |
3 |
|
| 2839 |
Open |
16.5.5.16 [lib.types.movedfrom] |
Self-move-assignment of library types, again |
Yes |
2 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 2153 |
LEWG |
20.2.2 [utility.swap] |
Narrowing of the non-member swap contract |
Yes |
2 |
|
| 2599 |
New |
20.2.6 [declval] |
Library incomplete type permission phrase is unclear |
No |
3 |
|
| 3346 |
Voting |
20.4.2 [pairs.pair] |
pair and tuple copy and move constructor have backwards specification |
Yes |
0 |
|
| 3342 |
New |
20.4.2 [pairs.pair] |
Library wording uses "initializes x with y", which is underspecified |
No |
3 |
|
| 2289 |
Open |
20.4.2 [pairs.pair] |
constexpr guarantees of defaulted functions still insufficient |
Yes |
3 |
|
| 3347 |
New |
20.4.3 [pairs.spec] |
std::pair<T, U> now requires T and U to be less-than-comparable |
Yes |
1 |
|
| 2766 |
New |
20.4.3 [pairs.spec] |
Swapping non-swappable types |
Yes |
3 |
|
| 3166 |
New |
20.4.4 [pair.astuple] |
No such descriptive element as Value: |
No |
3 |
|
| 3211 |
New |
20.5.3.1 [tuple.cnstr] |
std::tuple<> should be trivially constructible |
Yes |
|
|
| 2528 |
New |
20.5.3.1 [tuple.cnstr] |
Order of std::tuple construction unspecified |
No |
3 |
|
| 3155 |
Open |
20.5.3.1 [tuple.cnstr] |
tuple<any, any>{allocator_arg_t, an_allocator} |
Yes |
3 |
|
| 3121 |
Open |
20.5.3.1 [tuple.cnstr] |
tuple constructor constraints for UTypes&&... overloads |
Yes |
2 |
|
| 2933 |
New |
20.5.4 [tuple.creation] |
PR for LWG 2773 could be clearer |
Yes |
3 |
|
| 2472 |
New |
20.5.8 [tuple.rel] |
Heterogeneous comparisons in the standard library can result in ambiguities |
No |
3 |
|
| 532 |
LEWG |
20.5.8 [tuple.rel] |
Tuple comparison |
Yes |
|
348 |
| 2746 |
New |
20.6.3 [optional.optional] |
Inconsistency between requirements for emplace between optional and variant |
No |
3 |
|
| 2990 |
Open |
20.6.3 [optional.optional] |
optional::value_type is not always a value type |
Yes |
3 |
|
| 2825 |
LEWG |
20.6.3 [optional.optional] |
LWG 2756 breaks class template argument deduction for optional |
No |
2 |
|
| 2811 |
New |
20.6.3.1 [optional.ctor] |
"Selected constructor" wording is incorrect for optional/variant/any |
No |
3 |
|
| 2829 |
Open |
20.6.3.5 [optional.observe] |
LWG 2740 leaves behind vacuous words |
No |
2 |
|
| 2881 |
New |
20.7.3 [variant.variant] |
Adopt section III of P0308R0 |
No |
3 |
|
| 3215 |
New |
20.7.3.1 [variant.ctor] |
variant default constructor has vague constexpr requirements |
Yes |
2 |
|
| 2833 |
Open |
20.7.3.1 [variant.ctor] |
Library needs to specify what it means when it declares a function constexpr |
Yes |
2 |
|
| 3228 |
LEWG |
20.7.3.1 [variant.ctor] |
Surprising variant construction |
No |
2 |
|
| 2991 |
LEWG |
20.7.3.1 [variant.ctor] |
variant copy constructor missing noexcept(see below) |
Yes |
|
|
| 3069 |
New |
20.7.3.3 [variant.assign] |
Move assigning variant's subobject corrupts data |
Yes |
3 |
|
| 3052 |
LEWG |
20.7.7 [variant.visit] |
visit is underconstrained |
Yes |
2 |
|
| 3305 |
New |
20.8.4 [any.nonmembers] |
any_cast<void> |
Yes |
2 |
|
| 2348 |
Open |
20.9.2 [template.bitset] |
charT('1') is not the wide equivalent of '1' |
Yes |
3 |
|
| 3303 |
Voting |
20.10.2 [memory.syn] |
Bad "constexpr" marker for destroy/destroy_n |
Yes |
0 |
|
| 3374 |
New |
20.10.4 [pointer.conversion] |
P0653 + P1006 should have made the other std::to_address overload constexpr |
Yes |
|
|
| 2421 |
New |
20.10.6 [ptr.align] |
Non-specification of handling zero size in std::align [ptr.align] |
No |
3 |
|
| 3321 |
Voting |
20.10.8.2 [allocator.uses.construction] |
uninitialized_construct_using_allocator should use construct_at |
Yes |
0 |
|
| 3192 |
New |
20.10.8.2 [allocator.uses.construction] |
§[allocator.uses.construction] functions misbehave for const types |
Yes |
3 |
|
| 3307 |
Voting |
20.10.10 [default.allocator] |
std::allocator<void>().allocate(n) |
Yes |
0 |
|
| 3170 |
Open |
20.10.10 [default.allocator] |
is_always_equal added to std::allocator makes the standard library treat
derived types as always equal |
Yes |
2 |
|
| 3156 |
New |
20.10.11 [specialized.algorithms] |
ForwardIterator should only mean forward iterator |
Yes |
3 |
|
| 3063 |
New |
20.10.11 [specialized.algorithms] |
Parallel algorithms in <memory> are underspecified |
No |
3 |
|
| 3064 |
New |
20.10.11 [specialized.algorithms] |
How do uninitialized memory algorithms obtain pointer without undefined behavior? |
No |
3 |
|
| 3355 |
New |
20.10.11.5 [uninitialized.copy] |
The memory algorithms should support move-only input iterators introduced by P1207 |
Yes |
2 |
|
| 3159 |
New |
20.11.1.2 [unique.ptr.single] |
§[unique.ptr.single] requirements on deleter may be too strict |
No |
3 |
|
| 2262 |
Open |
20.11.1.2 [unique.ptr.single] |
Requirement for unique_ptr<T>::get_deleter()(p) to be able to destroy the unique_ptr |
Yes |
3 |
|
| 2762 |
Open |
20.11.1.2.4 [unique.ptr.single.observers] |
unique_ptr operator*() should be noexcept |
Yes |
3 |
|
| 3018 |
New |
20.11.3 [util.smartptr.shared] |
shared_ptr of function type |
Yes |
3 |
|
| 2594 |
New |
20.11.3 [util.smartptr.shared] |
Contradicting definition of empty shared_ptr on shared_ptr(nullptr, d) |
Yes |
3 |
|
| 3233 |
Voting |
20.11.3.1 [util.smartptr.shared.const] |
Broken requirements for shared_ptr converting constructors |
Yes |
0 |
|
| 2906 |
New |
20.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 |
|
| 2751 |
New |
20.11.3.2 [util.smartptr.shared.dest] |
shared_ptr deleter not specified to observe expired weak_ptr instances |
No |
4 |
|
| 3216 |
New |
20.11.3.6 [util.smartptr.shared.create] |
Rebinding the allocator before calling construct/destroy in allocate_shared |
Yes |
3 |
|
| 3210 |
New |
20.11.3.6 [util.smartptr.shared.create] |
allocate_shared is inconsistent about removing const from the pointer
passed to allocator construct and destroy |
Yes |
3 |
|
| 3195 |
New |
20.11.4.1 [util.smartptr.weak.const] |
What is the stored pointer value of an empty weak_ptr? |
Yes |
2 |
|
| 3304 |
Voting |
20.12.3 [mem.poly.allocator.class] |
Allocate functions of std::polymorphic_allocator should require [[nodiscard]] |
Yes |
3 |
|
| 3036 |
Open |
20.12.3 [mem.poly.allocator.class] |
polymorphic_allocator::destroy is extraneous |
Yes |
3 |
|
| 3310 |
Voting |
20.12.3.2 [mem.poly.allocator.mem] |
Replace SIZE_MAX with numeric_limits<size_t>::max() |
Yes |
0 |
|
| 3237 |
New |
20.12.3.2 [mem.poly.allocator.mem] |
LWG 3038 and 3190 have inconsistent PRs |
Yes |
|
|
| 2848 |
New |
20.12.5.2 [mem.res.pool.options] |
Pass-through threshold for pool allocator |
No |
3 |
|
| 3143 |
New |
20.12.6 [mem.res.monotonic.buffer] |
monotonic_buffer_resource growth policy is unclear |
No |
2 |
|
| 3120 |
Open |
20.12.6.2 [mem.res.monotonic.buffer.mem] |
Unclear behavior of monotonic_buffer_resource::release() |
Yes |
2 |
|
| 2690 |
LEWG |
20.14.4 [func.invoke] |
invoke<R> |
Yes |
|
|
| 3046 |
New |
20.14.5 [refwrap] |
Do not require reference_wrapper to support non-referenceable function types |
Yes |
3 |
|
| 3146 |
New |
20.14.5.5 [refwrap.helpers] |
Excessive unwrapping in std::ref/cref |
Yes |
3 |
|
| 2491 |
New |
20.14.7 [comparisons] |
std::less<T*> in constant expression |
Yes |
3 |
|
| 2547 |
New |
20.14.7 [comparisons] |
Container requirements (and other library text) should say "strict total order", not just "total order" |
No |
3 |
|
| 3238 |
New |
20.14.16.2.1 [func.wrap.func.con] |
Insufficiently-defined behavior of std::function deduction guides |
Yes |
|
|
| 2774 |
New |
20.14.16.2.1 [func.wrap.func.con] |
std::function construction vs assignment |
Yes |
3 |
|
| 2813 |
EWG |
20.14.16.2.1 [func.wrap.func.con] |
std::function should not return dangling references |
Yes |
2 |
|
| 1025 |
LEWG |
20.14.18 [unord.hash] |
The library should provide more specializations for std::hash |
No |
|
|
| 2290 |
Open |
20.15 [meta] |
Top-level "SFINAE"-based constraints should get a separate definition in Clause 17 |
Yes |
3 |
|
| 2452 |
Core |
20.15 [meta] |
is_constructible, etc. and default arguments |
No |
3 |
|
| 2845 |
New |
20.15.1 [meta.rqmts] |
enable_if, result_of, common_type and aligned_storage do not meet the definition
of TransformationTrait |
No |
3 |
|
| 2939 |
New |
20.15.2 [meta.type.synop] |
Some type-completeness constraints of traits are overspecified |
No |
2 |
|
| 3099 |
New |
20.15.2 [meta.type.synop] |
is_assignable<Incomplete&, Incomplete&> |
Yes |
|
|
| 2922 |
LEWG |
20.15.2 [meta.type.synop] |
The *_constant<> templates do not make use of template<auto> |
No |
|
|
| 2827 |
New |
20.15.4.3 [meta.unary.prop] |
is_trivially_constructible and non-trivial destructors |
No |
3 |
|
| 2496 |
New |
20.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 |
|
| 2116 |
Open |
20.15.4.3 [meta.unary.prop] |
is_nothrow_constructible and destructors |
No |
3 |
|
| 2358 |
Open |
20.15.4.3 [meta.unary.prop] |
Apparently-bogus definition of is_empty type trait |
Yes |
3 |
|
| 2077 |
Open |
20.15.4.3 [meta.unary.prop] |
Further incomplete constraints for type traits |
No |
3 |
|
| 3354 |
LEWG |
20.15.4.3 [meta.unary.prop] |
has_strong_structural_equality has a meaningless definition |
Yes |
1 |
|
| 3174 |
New |
20.15.6 [meta.rel] |
Precondition on is_convertible is too strong |
Yes |
3 |
|
| 3205 |
New |
20.15.7.6 [meta.trans.other] |
decay_t in the new common_type fallback should be remove_cvref_t |
Yes |
3 |
|
| 3152 |
New |
20.15.7.6 [meta.trans.other] |
common_type and common_reference have flaws in common |
Yes |
3 |
|
| 3373 |
New |
20.19.1 [charconv.syn] |
{to,from}_chars_result and format_to_n_result need the
"we really mean what we say" wording |
Yes |
|
|
| 3081 |
Open |
20.19.3 [charconv.from.chars] |
Floating point from_chars API does not distinguish between overflow and underflow |
Yes |
2 |
|
| 3082 |
Open |
20.19.3 [charconv.from.chars] |
from_chars specification regarding floating point rounding is inconsistent |
Yes |
2 |
|
| 3251 |
New |
20.20.2 [format.string] |
Are std::format alignment specifiers applied to string arguments? |
Yes |
2 |
|
| 3243 |
New |
20.20.2 [format.string] |
std::format and negative zeroes |
Yes |
2 |
|
| 3327 |
Voting |
20.20.2.2 [format.string.std] |
Format alignment specifiers vs. text direction |
Yes |
0 |
|
| 3290 |
New |
20.20.2.2 [format.string.std] |
Are std::format field widths code units, code points, or something else? |
Yes |
|
|
| 3248 |
New |
20.20.2.2 [format.string.std] |
std::format #b, #B, #o, #x, and #X
presentation types misformat negative numbers |
Yes |
2 |
|
| 3242 |
New |
20.20.2.2 [format.string.std] |
std::format: missing rules for arg-id in width and precision |
Yes |
|
|
| 3250 |
New |
20.20.2.2 [format.string.std] |
std::format: # (alternate form) for NaN and inf |
Yes |
|
|
| 3372 |
New |
20.20.3 [format.functions] |
vformat_to should not try to deduce Out twice |
Yes |
|
|
| 3336 |
New |
20.20.3 [format.functions] |
How does std::vformat handle exception thrown by formatters? |
Yes |
2 |
|
| 3340 |
New |
20.20.3 [format.functions] |
Formatting functions should throw on argument/format string mismatch in §[format.functions] |
Yes |
|
|
| 3371 |
New |
20.20.5.1 [format.arg] |
visit_format_arg and make_format_args are not hidden friends |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 2307 |
LEWG |
22 [containers] |
Should the Standard Library use explicit only when necessary? |
No |
2 |
|
| 2885 |
LEWG |
22 [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 |
|
|
| 2884 |
LEWG |
22 [containers] |
Relational operators for containers should sfinae; if the underlying type is not comparable, neither should the container be |
No |
|
|
| 3059 |
New |
22.2 [container.requirements] |
Wrong requirements for map-like associative container assignment? |
No |
3 |
|
| 3352 |
New |
22.2.1 [container.requirements.general] |
strong_equality isn't a thing |
No |
1 |
|
| 3028 |
New |
22.2.1 [container.requirements.general] |
Container requirements tables should distinguish const and non-const variables |
Yes |
3 |
|
| 2269 |
New |
22.2.1 [container.requirements.general] |
Container iterators and argument-dependent lookup |
No |
4 |
|
| 1521 |
Open |
22.2.1 [container.requirements.general] |
Requirements on internal pointer representations in containers |
Yes |
3 |
|
| 2321 |
Open |
22.2.1 [container.requirements.general] |
Moving containers should (usually) be required to preserve iterators |
Yes |
3 |
|
| 3297 |
New |
22.2.3 [sequence.reqmts] |
Useless sequence container requirement |
Yes |
3 |
|
| 2705 |
New |
22.2.3 [sequence.reqmts] |
Questionable precondition on Sequence containers a.assign(n, t) |
Yes |
3 |
|
| 2206 |
Open |
22.2.3 [sequence.reqmts] |
Inaccuracy in initializer_list constructor requirements |
Yes |
3 |
|
| 2743 |
New |
22.2.4.1 [container.node.overview] |
p0083r3 node_handle private members missing "exposition only" comment |
Yes |
3 |
|
| 3227 |
New |
22.2.6 [associative.reqmts] |
Ambiguity issue for extract in ordered and unordered associative containers |
Yes |
3 |
|
| 2844 |
New |
22.2.6 [associative.reqmts] |
Stability of a_uniq.insert(i, j) |
No |
3 |
|
| 2362 |
New |
22.2.6 [associative.reqmts] |
unique, associative emplace() should not move/copy the mapped_type constructor
arguments when no insertion happens |
No |
3 |
|
| 2227 |
Open |
22.2.6 [associative.reqmts] |
Stateful comparison objects in associative containers |
No |
3 |
|
| 2215 |
Open |
22.2.6 [associative.reqmts] |
(unordered) associative container functors should be CopyConstructible |
Yes |
3 |
|
| 1175 |
Open |
22.2.7 [unord.req] |
unordered complexity |
Yes |
3 |
|
| 2198 |
Open |
22.2.7 [unord.req] |
max_load_factor(z) makes no strong guarantees, but bans useful behavior |
Yes |
3 |
|
| 2189 |
Open |
22.2.7.1 [unord.req.except] |
Throwing swap breaks unordered containers' state |
No |
3 |
|
| 2335 |
New |
22.3.7 [array] |
array<array<int, 3>, 4> should be layout-compatible with int[4][3] |
No |
3 |
|
| 3219 |
New |
22.3.7.1 [array.overview] |
std::array overview container requirements are incorrect |
Yes |
3 |
|
| 2823 |
Open |
22.3.7.1 [array.overview] |
std::array initialization is still not permissive enough |
Yes |
3 |
|
| 2157 |
Open |
22.3.7.5 [array.zero] |
How does std::array<T,0> initialization work when T is not default-constructible? |
Yes |
3 |
|
| 3308 |
New |
22.3.8.4 [deque.modifiers] |
vector and deque iterator erase invalidates elements even when no change occurs |
Yes |
3 |
|
| 3088 |
New |
22.3.9.6 [forwardlist.ops] |
forward_list::merge behavior unclear when passed *this |
Yes |
3 |
|
| 2997 |
New |
22.3.10.5 [list.ops] |
LWG 491 and the specification of {forward_,}list::unique |
Yes |
3 |
|
| 2158 |
Open |
22.3.11.3 [vector.capacity] |
Conditional copy/move in std::vector |
Yes |
3 |
|
| 1422 |
Open |
22.3.12 [vector.bool] |
vector<bool> iterators are not random access |
No |
3 |
|
| 2713 |
New |
22.5 [unord] |
More missing allocator-extended constructors for unordered containers |
Yes |
3 |
|
| 3189 |
New |
22.6.5 [priority.queue] |
Missing requirement for std::priority_queue |
No |
3 |
|
| 3161 |
Open |
22.6.6 [stack] |
Container adapters mandate use of emplace_back but don't require it |
Yes |
|
|
| 3369 |
New |
22.7.3.1 [span.overview] |
span's deduction-guide for built-in arrays doesn't work |
Yes |
|
|
| 3203 |
New |
22.7.3.1 [span.overview] |
span element access invalidation |
Yes |
2 |
|
| 3358 |
Tentatively Ready |
22.7.3.2 [span.cons] |
§[span.cons] is mistaken that to_address can throw |
Yes |
0 |
|
| 3255 |
New |
22.7.3.2 [span.cons] |
span's array constructor is too strict |
Yes |
2 |
|
| 3320 |
Voting |
22.7.3.7 [span.iterators] |
span::cbegin/cend methods produce different results than std::[ranges::]cbegin/cend |
Yes |
0 |
|
| 3212 |
New |
22.7.3.9 [span.tuple] |
tuple_element_t<1, const span<int, 42>> is const int |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 1213 |
Open |
23.3 [iterator.requirements] |
Meaning of valid and singular iterator underspecified |
No |
4 |
|
| 3110 |
New |
23.3.1 [iterator.requirements.general] |
Contiguous Iterators should always be Random-Access |
Yes |
3 |
|
| 2375 |
New |
23.3.1 [iterator.requirements.general] |
Is [iterator.requirements.general]/9 too broadly applied? |
No |
3 |
|
| 3283 |
New |
23.3.2.3 [iterator.traits] |
Types satisfying input_iterator but not equality_comparable look like
C++17 output iterators |
Yes |
1 |
|
| 3289 |
New |
23.3.2.3 [iterator.traits] |
Cannot opt out of C++17 iterator-ness without also opting out of C++20 iterator-ness |
Yes |
1 |
|
| 3287 |
New |
23.3.2.3 [iterator.traits] |
Exposition-only cpp17-input-iterator concept is needlessly complex |
Yes |
3 |
|
| 3299 |
Voting |
23.3.3.1 [iterator.cust.move] |
Pointers don't need customized iterator behavior |
Yes |
0 |
|
| 3247 |
New |
23.3.3.1 [iterator.cust.move] |
ranges::iter_move should perform ADL-only lookup of iter_move |
Yes |
|
|
| 3376 |
New |
23.3.4.4 [iterator.concept.winc] |
"integer-like class type" is too restrictive |
No |
|
|
| 3367 |
New |
23.3.4.4 [iterator.concept.winc] |
Integer-class conversions should not throw |
Yes |
|
|
| 3366 |
New |
23.3.4.4 [iterator.concept.winc] |
Narrowing conversions between integer and integer-class types |
No |
|
|
| 3284 |
Voting |
23.3.4.13 [iterator.concept.random.access] |
random_access_iterator semantic constraints accidentally promote difference type
using unary negate |
Yes |
0 |
|
| 2962 |
Open |
23.3.5.2 [input.iterators] |
Iterators of Containers of move-only types do not model InputIterator |
Yes |
2 |
|
| 484 |
Open |
23.3.5.2 [input.iterators] |
Convertible to T |
No |
2 |
|
| 2035 |
Open |
23.3.5.3 [output.iterators] |
Output iterator requirements are broken |
Yes |
3 |
|
| 2038 |
Open |
23.3.5.3 [output.iterators] |
Missing definition for incrementable iterator |
No |
3 |
|
| 3236 |
New |
23.3.5.6 [random.access.iterators] |
Random access iterator requirements lack limiting relational operators domain to comparing
those from the same range |
Yes |
|
|
| 3344 |
New |
23.4.2 [iterator.operations] |
advance(i, most-negative) and prev(i, most-negative) |
Yes |
3 |
|
| 3197 |
New |
23.4.2 [iterator.operations] |
std::prev should not require BidirectionalIterator |
Yes |
3 |
|
| 2931 |
Open |
23.4.2 [iterator.operations] |
Missed optimization opportunity with single-argument std::next |
No |
3 |
|
| 3306 |
New |
23.4.3.1 [range.iter.op.advance] |
ranges::advance violates its preconditions |
Yes |
2 |
|
| 2858 |
New |
23.5.1 [reverse.iterators] |
LWG 2472: actually an incompatibility with C++03 |
Yes |
4 |
|
| 2595 |
New |
23.5.1.1 [reverse.iterator] |
reverse_iterator::operator[]'s return type revisited |
Yes |
3 |
|
| 3265 |
New |
23.5.3.3 [move.iter.cons] |
move_iterator's conversions are more broken after P1207 |
Yes |
2 |
|
| 3293 |
New |
23.5.3.8 [move.iter.nonmember] |
move_iterator operator+() has incorrect constraints |
Yes |
3 |
|
| 3188 |
New |
23.6.3 [istreambuf.iterator] |
istreambuf_iterator::pointer should not be unspecified |
Yes |
3 |
|
| 3107 |
New |
23.6.3 [istreambuf.iterator] |
istreambuf_iterator has public exposition-only member |
Yes |
4 |
|
| 2366 |
New |
23.6.3 [istreambuf.iterator] |
istreambuf_iterator end-of-stream equality |
No |
3 |
|
| 3108 |
New |
23.6.3.1 [istreambuf.iterator.proxy] |
istreambuf_iterator::proxy::operator* should be const |
Yes |
3 |
|
| 3300 |
Voting |
23.7 [iterator.range] |
Non-array ssize overload is underconstrained |
Yes |
3 |
|
| 3207 |
Tentatively NAD |
23.7 [iterator.range] |
N in ssize(const T (&)[N]) should be size_t |
Yes |
|
|
| 2457 |
New |
23.7 [iterator.range] |
std::begin() and std::end() do not support multi-dimensional arrays correctly |
No |
3 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 3302 |
Voting |
24.2 [ranges.syn] |
Range adaptor objects keys and values are unspecified |
Yes |
1 |
|
| 3351 |
Voting |
24.2 [ranges.syn] |
ranges::enable_safe_range should not be constrained |
Yes |
0 |
|
| 3335 |
New |
24.2 [ranges.syn] |
Resolve C++20 NB comments US 273 and GB 274 |
Yes |
1 |
|
| 3258 |
New |
24.3.1 [range.access.begin] |
Range access and initializer_list |
Yes |
3 |
|
| 3333 |
New |
24.3.3 [range.access.cbegin] |
ranges::cbegin/ranges::cend, (and maybe ranges::crbegin/ranges::crend) are under-specified to allow rvalue-arrays |
Yes |
|
|
| 3368 |
New |
24.3.9 [range.prim.size] |
Exactly when does size return end - begin? |
Yes |
|
|
| 3361 |
New |
24.4.2 [range.range] |
safe_range<SomeRange&> case |
Yes |
3 |
|
| 3264 |
Voting |
24.4.3 [range.sized] |
sized_range and ranges::size redundantly use disable_sized_range |
Yes |
1 |
|
| 3326 |
Voting |
24.4.4 [range.view] |
enable_view has false positives |
Yes |
0 |
|
| 3375 |
New |
24.4.5 [range.refinements] |
decay in viewable_range should be remove_cvref |
Yes |
|
|
| 3281 |
Voting |
24.5.3 [range.subrange] |
Conversion from pair-like types to subrange is a silent semantic promotion |
Yes |
1 |
|
| 3282 |
Open |
24.5.3 [range.subrange] |
subrange converting constructor should disallow derived to base conversions |
Yes |
1 |
|
| 3292 |
Voting |
24.6.3.2 [range.iota.view] |
iota_view is under-constrained |
Yes |
|
|
| 3291 |
Voting |
24.6.3.3 [range.iota.iterator] |
iota_view::iterator has the wrong iterator_category |
Yes |
0 |
|
| 3280 |
Voting |
24.7.4.2 [range.filter.view] |
View converting constructors can cause constraint recursion and are unneeded |
Yes |
1 |
|
| 3325 |
Voting |
24.7.5.2 [range.transform.view] |
Constrain return type of transformation function for transform_view |
Yes |
0 |
|
| 3301 |
New |
24.7.5.3 [range.transform.iterator] |
transform_view::iterator has incorrect iterator_category |
Yes |
1 |
|
| 3286 |
Voting |
24.7.6.2 [range.take.view] |
ranges::size is not required to be valid after a call to ranges::begin on an input range |
Yes |
0 |
|
| 3364 |
Tentatively Ready |
24.7.7.2 [range.take.while.view] |
Initialize data members of ranges and their iterators |
Yes |
0 |
|
| 3298 |
New |
24.7.7.2 [range.take.while.view] |
Range adaptors introduced by P1035 do not require viewable_range |
Yes |
|
|
| 3363 |
New |
24.7.9.2 [range.drop.while.view] |
drop_while_view should opt-out of sized_range |
Yes |
1 |
|
| 3278 |
New |
24.7.10.2 [range.join.view] |
join_view<V>::iterator<true> tries to write through const join_view ptr |
Yes |
2 |
|
| 3322 |
Tentatively Resolved |
24.7.10.2 [range.join.view] |
Add join_view::base() member function |
Yes |
0 |
|
| 3313 |
Voting |
24.7.10.3 [range.join.iterator] |
join_view::iterator::operator-- is incorrectly constrained |
Yes |
0 |
|
| 3365 |
Tentatively NAD |
24.7.10.3 [range.join.iterator] |
Rename ref-is-glvalue to deref-is-ref |
Yes |
0 |
|
| 3323 |
Voting |
24.7.15.2 [range.elements.view] |
has-tuple-element helper concept needs convertible_to |
Yes |
0 |
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 2592 |
New |
27.2 [time.syn] |
Require that chrono::duration_casts from smaller durations to larger durations do not overflow |
Yes |
4 |
|
| 3123 |
New |
27.5 [time.duration] |
duration constructor from representation shouldn't be effectively non-throwing |
Yes |
3 |
|
| 3090 |
New |
27.5.1 [time.duration.cons] |
What is §[time.duration.cons]p4's "no overflow is induced in the conversion" intended to mean? |
No |
3 |
|
| 3050 |
Open |
27.5.1 [time.duration.cons] |
Conversion specification problem in chrono::duration constructor |
Yes |
3 |
|
| 2383 |
Open |
27.5.8 [time.duration.literals] |
Overflow cannot be ill-formed for chrono::duration integer literals |
No |
3 |
|
| 3317 |
Voting |
27.5.10 [time.duration.io] |
Incorrect operator<< for floating-point durations |
Yes |
0 |
|
| 3314 |
New |
27.5.10 [time.duration.io] |
Is stream insertion behavior locale dependent when Period::type is micro? |
Yes |
2 |
|
| 3125 |
Open |
27.5.10 [time.duration.io] |
duration streaming precondition should be a SFINAE condition |
Yes |
2 |
|
| 3318 |
Voting |
27.7.1.1 [time.clock.system.overview] |
Clarify whether clocks can represent time before their epoch |
Yes |
0 |
|
| 3316 |
Voting |
27.7.2.1 [time.clock.utc.overview] |
Correctly define epoch for utc_clock / utc_timepoint |
Yes |
0 |
|
| 3260 |
New |
27.8 [time.cal] |
year_month* arithmetic rejects durations convertible to years |
Yes |
2 |
|
| 3319 |
Voting |
27.11.1 [time.zone.general] |
Properly reference specification of IANA time zone database |
Yes |
0 |
|
| 3294 |
Voting |
27.11.7.1 [time.zone.zonedtime.overview] |
zoned_time deduction guides misinterprets string/char* |
Yes |
0 |
|
| 3226 |
New |
27.11.7.2 [time.zone.zonedtime.ctor] |
zoned_time constructor from string_view should accept
zoned_time<Duration2, TimeZonePtr2> |
Yes |
|
|
| 3359 |
New |
27.11.8 [time.zone.leap] |
<chrono> leap second support should allow for negative leap seconds |
Yes |
3 |
|
| 3332 |
Voting |
27.12 [time.format] |
Issue in §[time.format] |
Yes |
0 |
|
| 3270 |
New |
27.12 [time.format] |
Parsing and formatting %j with durations |
Yes |
2 |
|
| 3262 |
New |
27.12 [time.format] |
Formatting of negative durations is not specified |
Yes |
2 |
|
| 3269 |
New |
27.13 [time.parse] |
Parse manipulators do not specify the result of the extraction from stream |
Yes |
2 |
|
| 3271 |
New |
27.13 [time.parse] |
Parsing functions should save and restore stream format state |
Yes |
3 |
|
| 3252 |
New |
27.13 [time.parse] |
Parse locale's aware modifiers for commands are not consistent
with POSIX spec |
Yes |
|
|
| Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
| 423 |
Open |
29 [input.output] |
Effects of negative streamsize in iostreams |
Yes |
3 |
|
| 2675 |
New |
29.5.3.6 [ios.base.callback] |
register_callback can fail |
No |
3 |
|
| 3118 |
New |
29.5.4.2 [fpos.operations] |
fpos equality comparison unspecified |
No |
4 |
|
| 2808 |
Tentatively Resolved |
29.5.4.2 [fpos.operations] |
Requirements for fpos and stateT |
No |
4 |
|
| 2832 |
Tentatively Resolved |
29.5.4.2 [fpos.operations] |
§[fpos.operations] strange requirement for P(i) |
No |
3 |
|
| 2214 |
Open |
29.5.5.2 [basic.ios.cons] |
Clarify basic_ios::init call restrictions |
Yes |
4 |
|
| 2504 |
New |
29.6.3 [streambuf] |
basic_streambuf is not an abstract class |
No |
3 |
|
| 2349 |
Open |
29.7.4.2.1 [istream.formatted.reqmts] |
Clarify input/output function rethrow behavior |
Yes |
3 |
|
| 2498 |
New |
29.7.4.5 [istream.rvalue] |
operator>>(basic_istream&&, T&&) returns basic_istream&, but should probably return
basic_istream&& |
No |
3 |
|
| 2342 |
New |
29.7.5.1 [ostream] |
User conversion to wchar_t const* or to wchar_t not invoked for operator<< |
Yes |
4 |
|
| 2497 |
New |
29.7.5.1.3 [ostream.sentry] |
Use of uncaught_exception() |
Yes |
3 |
|
| 1203 |
Open |
29.7.5.5 [ostream.rvalue] |
More useful rvalue stream insertion |
Yes |
2 |
|
| 2984 |
New |
29.7.7 [ext.manip] |
put_money(99) is unnecessarily undefined |
Yes |
3 |
|
| 3309 |
New |
29.8 [string.streams] |
Is <ios> implicitly #included by <sstream>, <fstream> etc.? |
No |
3 |
|
| 3006 |
New |
29.8.2.1 [stringbuf.cons] |
Constructing a basic_stringbuf from a string — where does the allocator come from? |
No |
3 |
|
| 3097 |
New |
29.8.2.4 [stringbuf.virtuals] |
basic_stringbuf seekoff effects trigger undefined behavior and have contradictory returns |
No |
3 |
|
| 2286 |
Open |
29.8.2.4 [stringbuf.virtuals] |
stringbuf::underflow() underspecified |
Yes |
4 |
|
| 3334 |
New |
29.10.3 [syncstream.osyncstream] |
basic_osyncstream move assignment and destruction calls basic_syncbuf::emit() twice |
No |
|
|
| 3098 |
New |
29.11.7.4.9 [fs.path.decompose] |
Misleading example for filesystem::path::filename() |
Yes |
3 |
|
| 2947 |
New |
29.11.9.1 [fs.enum.path.format] |
Clarify several filesystem terms |
No |
3 |
|
| 3078 |
New |
29.11.11 [fs.class.directory.entry] |
directory_entry, directory_iterator and recursive_directory_iterator perform needless path copies |
No |
3 |
|
| 3171 |
Open |
29.11.11 [fs.class.directory.entry] |
LWG 2989 breaks directory_entry stream insertion |
Yes |
2 |
|
| 2708 |
Open |
29.11.13.1 [fs.rec.dir.itr.members] |
recursive_directory_iterator::recursion_pending() is incorrectly specified |
Yes |
2 |
|
| 3057 |
Open |
29.11.14.3 [fs.op.copy] |
Correct copy_options handling |
Yes |
2 |
|
| 3056 |
New |
29.11.14.4 [fs.op.copy.file] |
copy_file() copies which attributes? |
Yes |
3 |
|