Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
2949 |
New |
17 [library] |
Unclear complexity requirements: space vs. time |
No |
|
|
2392 |
New |
17.3.15 [defns.ntcts] |
"character type" is used but not defined |
No |
3 |
|
2136 |
Open |
17.4.1 [structure] |
Postconditions vs. exceptions |
No |
3 |
|
2292 |
New |
17.4.1.4 [structure.specifications] |
Find a better phrasing for "shall not participate in overload resolution" |
No |
3 |
|
2692 |
Tentatively NAD |
17.4.2.1.4 [bitmask.types] |
Overspecification of lvalueness of bitmask elements |
No |
3 |
|
2818 |
New |
17.5.1.1 [contents] |
"::std::" everywhere rule needs tweaking |
No |
2 |
|
2146 |
Open |
17.5.3.1 [utility.arg.requirements] |
Are reference types Copy/Move-Constructible/Assignable or Destructible? |
No |
2 |
|
2152 |
LEWG |
17.5.3.2 [swappable.requirements] |
Instances of standard container types are not swappable |
Yes |
3 |
|
2114 |
Open |
17.5.3.3 [nullablepointer.requirements] |
Incorrect "contextually convertible to bool" requirements |
Yes |
3 |
|
2593 |
Tentatively Ready |
17.5.3.5 [allocator.requirements] |
Moved-from state of Allocators |
Yes |
4 |
|
2461 |
New |
17.5.3.5 [allocator.requirements] |
Interaction between allocators and container exception safety guarantees |
No |
3 |
|
2954 |
Tentatively Ready |
17.5.4 [constraints] |
Specialization of the convenience variable templates should be prohibited |
Yes |
|
|
2139 |
Open |
17.5.4.2.1 [namespace.std] |
What is a user-defined type? |
Yes |
4 |
|
2891 |
New |
17.5.5 [conforming] |
Relax library requirements on volatile types |
No |
|
|
2563 |
New |
17.5.5.5 [member.functions] |
LWG 2259 relaxes requirements, perhaps unintentionally |
No |
2 |
|
2695 |
New |
17.5.5.5 [member.functions] |
"As if" unclear in [member.functions] |
No |
3 |
|
2892 |
New |
17.5.5.6 [constexpr.functions] |
Relax the prohibition on libraries adding constexpr |
Yes |
|
|
2414 |
Open |
17.5.5.8 [reentrancy] |
Member function reentrancy should be implementation-defined |
Yes |
3 |
|
2839 |
New |
17.5.5.15 [lib.types.movedfrom] |
Self-move-assignment of library types, again |
Yes |
2 |
|
Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
2893 |
New |
20 [utilities] |
Parsing Hexadecimally in P0067R4 |
No |
|
|
2955 |
New |
20.2 [utility] |
to_chars / from_chars depend on std::string |
No |
|
|
1289 |
LEWG |
20.2 [utility] |
Generic casting requirements for smart pointers |
Yes |
|
|
2800 |
New |
20.2.3 [utility.swap] |
constexpr swap |
No |
3 |
|
2153 |
LEWG |
20.2.3 [utility.swap] |
Narrowing of the non-member swap contract |
Yes |
2 |
|
2599 |
New |
20.2.7 [declval] |
Library incomplete type permission phrase is unclear |
No |
3 |
|
2958 |
New |
20.4.2 [pairs.pair] |
Moves improperly defined as deleted |
Yes |
|
|
2289 |
Open |
20.4.2 [pairs.pair] |
constexpr guarantees of defaulted functions still insufficient |
Yes |
3 |
|
2766 |
New |
20.4.3 [pairs.spec] |
Swapping non-swappable types |
Yes |
3 |
|
2974 |
Tentatively Ready |
20.4.4 [pair.astuple] |
Diagnose out of bounds tuple_element/variant_alternative |
Yes |
|
|
2899 |
New |
20.5 [tuple] |
is_(nothrow_)move_constructible and tuple, optional and unique_ptr |
Yes |
|
|
2528 |
New |
20.5.3.1 [tuple.cnstr] |
Order of std::tuple construction unspecified |
No |
3 |
|
2419 |
LEWG |
20.5.3.1 [tuple.cnstr] |
Clang's libc++ extension to std::tuple |
No |
|
|
2933 |
New |
20.5.3.4 [tuple.creation] |
PR for LWG 2773 could be clearer |
Yes |
3 |
|
1201 |
LEWG |
20.5.3.4 [tuple.creation] |
Do we always want to unwrap ref-wrappers in make_tuple |
Yes |
|
|
2472 |
New |
20.5.3.8 [tuple.rel] |
Heterogeneous comparisons in the standard library can result in ambiguities |
No |
3 |
|
532 |
LEWG |
20.5.3.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 |
|
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 |
New |
20.6.3.5 [optional.observe] |
LWG 2740 leaves behind vacuous words |
No |
2 |
|
2945 |
New |
20.6.8 [optional.comp_with_t] |
Order of template parameters in optional comparisons |
No |
|
|
2971 |
New |
20.7.3 [variant.variant] |
variant should require Destructible types |
Yes |
|
|
2901 |
New |
20.7.3 [variant.variant] |
Variants cannot properly support allocators |
Yes |
|
|
2902 |
New |
20.7.3 [variant.variant] |
variant should only support complete types |
Yes |
|
|
2881 |
New |
20.7.3 [variant.variant] |
Adopt section III of P0308R0 |
No |
|
|
2833 |
New |
20.7.3.1 [variant.ctor] |
Library needs to specify what it means when it declares a function constexpr |
Yes |
2 |
|
2970 |
New |
20.7.7 [variant.visit] |
Return type of std::visit misspecified |
No |
|
|
2886 |
New |
20.8.3.4 [any.observers] |
Keep the empty() functions in any |
No |
|
|
2348 |
Open |
20.9.2 [template.bitset] |
charT('1') is not the wide equivalent of '1' |
Yes |
3 |
|
2421 |
New |
20.10.5 [ptr.align] |
Non-specification of handling zero size in std::align [ptr.align] |
No |
3 |
|
2089 |
EWG |
20.10.9.1 [allocator.members] |
std::allocator::construct should use uniform initialization |
Yes |
2 |
|
2948 |
New |
20.11.1 [unique.ptr] |
unique_ptr does not define operator<< for stream output |
Yes |
|
|
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 |
|
2944 |
New |
20.11.1.2.1 [unique.ptr.single.ctor] |
LWG 2905 accidentally removed requirement that construction of the deleter doesn't throw an exception |
Yes |
|
|
2762 |
LEWG |
20.11.1.2.4 [unique.ptr.single.observers] |
unique_ptr operator*() should be noexcept |
Yes |
3 |
|
2594 |
New |
20.11.2.2 [util.smartptr.shared] |
Contradicting definition of empty shared_ptr on shared_ptr(nullptr, d) |
Yes |
3 |
|
1406 |
LEWG |
20.11.2.2 [util.smartptr.shared] |
Support hashing smart-pointers based on owner |
Yes |
|
|
2906 |
New |
20.11.2.2.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 |
|
|
2751 |
New |
20.11.2.2.2 [util.smartptr.shared.dest] |
shared_ptr deleter not specified to observe expired weak_ptr instances |
No |
4 |
|
2907 |
New |
20.11.2.2.2 [util.smartptr.shared.dest] |
Semantics for destroying the deleter and the control-block of a shared_ptr are unclear |
No |
|
|
2337 |
Tentatively NAD |
20.11.2.2.5 [util.smartptr.shared.obs] |
shared_ptr operator*() should not be noexcept |
No |
2 |
|
2776 |
New |
20.11.2.2.5 [util.smartptr.shared.obs] |
shared_ptr unique() and use_count() |
No |
2 |
|
2070 |
Open |
20.11.2.2.6 [util.smartptr.shared.create] |
allocate_shared should use allocator_traits<A>::construct |
Yes |
2 |
|
2964 |
New |
20.11.2.2.9 [util.smartptr.shared.cast] |
Apparently redundant requirement for dynamic_pointer_cast |
Yes |
|
|
2942 |
Tentatively Ready |
20.11.2.3.5 [util.smartptr.weak.obs] |
LWG 2873's resolution missed weak_ptr::owner_before |
Yes |
|
|
2980 |
New |
20.11.2.6 [util.smartptr.shared.atomic] |
Cannot compare_exchange empty pointers |
Yes |
|
|
2843 |
New |
20.12.2.2 [mem.res.private] |
Unclear behavior of std::pmr::memory_resource::do_allocate() |
Yes |
3 |
|
2969 |
New |
20.12.3.2 [mem.poly.allocator.mem] |
polymorphic_allocator::construct() shouldn't pass resource() |
Yes |
|
|
2975 |
New |
20.12.3.2 [mem.poly.allocator.mem] |
Missing case for pair construction in scoped and polymorphic allocators |
Yes |
|
|
2961 |
Tentatively Ready |
20.12.4 [mem.res.global] |
Bad postcondition for set_default_resource |
Yes |
|
|
2848 |
New |
20.12.5.2 [mem.res.pool.options] |
Pass-through threshold for pool allocator |
No |
3 |
|
2717 |
Tentatively NAD |
20.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor uses forward to do move's job |
Yes |
|
|
2511 |
New |
20.13.4 [allocator.adaptor.members] |
scoped_allocator_adaptor piecewise construction does not require CopyConstructible |
No |
3 |
|
2894 |
Open |
20.14.4 [func.invoke] |
The function template std::apply() is required to be constexpr, but std::invoke() isn't |
Yes |
|
|
2690 |
LEWG |
20.14.4 [func.invoke] |
invoke<R> |
Yes |
|
|
2981 |
New |
20.14.5 [refwrap] |
Remove redundant deduction guides from standard library |
Yes |
|
|
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 |
|
2957 |
New |
20.14.11.3 [func.bind.bind] |
bind's specification doesn't apply the cv-qualification of the call wrapper to the callable object |
Yes |
|
|
2774 |
New |
20.14.13.2.1 [func.wrap.func.con] |
std::function construction vs assignment |
No |
3 |
|
2813 |
New |
20.14.13.2.1 [func.wrap.func.con] |
std::function should not return dangling references |
Yes |
2 |
|
1025 |
LEWG |
20.14.15 [unord.hash] |
The library should provide more specializations for std::hash |
No |
|
|
1317 |
LEWG |
20.14.15 [unord.hash] |
make_hash |
Yes |
|
|
2290 |
Open |
20.15 [meta] |
Top-level "SFINAE"-based constraints should get a separate definition in Clause 17 |
Yes |
3 |
|
2040 |
LEWG |
20.15 [meta] |
Missing type traits related to is_convertible |
Yes |
|
|
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 |
|
2910 |
New |
20.15.2 [meta.type.synop] |
Template deduction and integral_constant |
Yes |
|
|
2922 |
New |
20.15.2 [meta.type.synop] |
The *_constant<> templates do not make use of template<auto> |
No |
|
|
2871 |
New |
20.15.2 [meta.type.synop] |
User specializations of type traits should be ill-formed |
Yes |
|
|
2797 |
Open |
20.15.2 [meta.type.synop] |
Trait precondition violations |
Yes |
2 |
|
2972 |
New |
20.15.4.3 [meta.unary.prop] |
What is is_trivially_destructible_v<int>? |
Yes |
|
|
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 |
|
2827 |
New |
20.15.4.3 [meta.unary.prop] |
is_trivially_constructible and non-trivial destructors |
No |
3 |
|
2077 |
Open |
20.15.4.3 [meta.unary.prop] |
Further incomplete constraints for 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 |
|
2979 |
New |
20.15.7.6 [meta.trans.other] |
aligned_union should require complete object types |
Yes |
|
|
2569 |
Open |
20.15.8 [meta.logical] |
conjunction and disjunction requirements are too strict |
Yes |
2 |
|
2587 |
Open |
20.15.8 [meta.logical] |
"Convertible to bool" requirement in conjunction and disjunction |
Yes |
3 |
|
1121 |
LEWG |
20.16.4 [ratio.arithmetic] |
Support for multiple arguments |
Yes |
|
|
2592 |
New |
20.17.2 [time.syn] |
Require that chrono::duration_casts from smaller durations to larger durations do not overflow |
Yes |
4 |
|
2383 |
Open |
20.17.5.8 [time.duration.literals] |
Overflow cannot be ill-formed for chrono::duration integer literals |
No |
3 |
|
935 |
LEWG |
20.17.7 [time.clock] |
clock error handling needs to be specified |
Yes |
|
|
2909 |
New |
20.19.3 [execpol.type] |
User specializations of is_execution_policy should be ill-formed |
No |
|
|
Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
2884 |
New |
23 [containers] |
Relational operators for containers should sfinae; if the underlying type is not comparable, neither should the container be |
No |
|
|
2885 |
New |
23 [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 |
|
|
2307 |
Open |
23 [containers] |
Should the Standard Library use explicit only when necessary? |
No |
2 |
|
1242 |
LEWG |
23 [containers] |
Enable SCARY iterators |
Yes |
|
|
760 |
Tentatively NAD |
23.2 [container.requirements] |
The emplace issue |
Yes |
2 |
|
2269 |
New |
23.2.1 [container.requirements.general] |
Container iterators and argument-dependent lookup |
No |
4 |
|
2321 |
Open |
23.2.1 [container.requirements.general] |
Moving containers should (usually) be required to preserve iterators |
Yes |
2 |
|
1521 |
LEWG |
23.2.1 [container.requirements.general] |
Requirements on internal pointer representations in containers |
Yes |
|
|
2705 |
New |
23.2.3 [sequence.reqmts] |
Questionable precondition on Sequence containers a.assign(n, t) |
Yes |
3 |
|
2206 |
Open |
23.2.3 [sequence.reqmts] |
Inaccuracy in initializer_list constructor requirements |
No |
3 |
|
2743 |
New |
23.2.4.1 [container.node.overview] |
p0083r3 node_handle private members missing "exposition only" comment |
No |
3 |
|
2362 |
New |
23.2.6 [associative.reqmts] |
unique, associative emplace() should not move/copy the mapped_type constructor
arguments when no insertion happens |
No |
3 |
|
2772 |
New |
23.2.6 [associative.reqmts] |
Inconsistency in the insert(node) interface |
No |
2 |
|
2844 |
New |
23.2.6 [associative.reqmts] |
Stability of a_uniq.insert(i, j) |
No |
3 |
|
2215 |
Open |
23.2.6 [associative.reqmts] |
(unordered) associative container functors should be CopyConstructible |
Yes |
3 |
|
2227 |
Open |
23.2.6 [associative.reqmts] |
Stateful comparison objects in associative containers |
No |
3 |
|
2977 |
New |
23.2.7 [unord.req] |
unordered_meow::merge() has incorrect Throws: clause |
Yes |
|
|
1175 |
Open |
23.2.7 [unord.req] |
unordered complexity |
Yes |
3 |
|
2198 |
Open |
23.2.7 [unord.req] |
max_load_factor(z) makes no strong guarantees, but bans useful behavior |
Yes |
3 |
|
1188 |
LEWG |
23.2.7 [unord.req] |
Unordered containers should have a minimum load factor as well as a maximum |
Yes |
|
|
2831 |
LEWG |
23.2.7 [unord.req] |
Equality can be defined when Hash function objects have different behaviour |
Yes |
|
|
2189 |
Open |
23.2.7.1 [unord.req.except] |
Throwing swap breaks unordered containers' state |
No |
3 |
|
2335 |
New |
23.3.7 [array] |
array<array<int, 3>, 4> should be layout-compatible with int[4][3] |
No |
3 |
|
2897 |
New |
23.3.7.1 [array.overview] |
array::iterator and array::const_iterator should be literal types |
Yes |
2 |
|
2823 |
New |
23.3.7.1 [array.overview] |
std::array initialization is still not permissive enough |
Yes |
2 |
|
2157 |
Open |
23.3.7.8 [array.zero] |
How does std::array<T,0> initialization work when T is not default-constructible? |
Yes |
3 |
|
2953 |
New |
23.3.8.4 [deque.modifiers] |
LWG 2853 should apply to deque::erase too |
Yes |
|
|
2158 |
Open |
23.3.11.3 [vector.capacity] |
Conditional copy/move in std::vector |
Yes |
2 |
|
2164 |
Open |
23.3.11.5 [vector.modifiers] |
What are the semantics of vector.emplace(vector.begin(), vector.back())? |
No |
2 |
|
1422 |
Open |
23.3.12 [vector.bool] |
vector<bool> iterators are not random access |
No |
3 |
|
2713 |
New |
23.5 [unord] |
More missing allocator-extended constructors for unordered containers |
Yes |
3 |
|
2982 |
New |
23.5.6.1 [unord.set.overview] |
Making size_type consistent in associative container deduction guides |
Yes |
|
|
2783 |
Tentatively Ready |
23.6.4.1 [queue.defn] |
stack::emplace() and queue::emplace() should return decltype(auto) |
Yes |
2 |
|
Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
423 |
LEWG |
27 [input.output] |
effects of negative streamsize in iostreams |
Yes |
|
|
2600 |
LEWG |
27.5.3.5 [ios.base.storage] |
ios_base must store inaccessible iostate flags |
No |
|
|
2675 |
New |
27.5.3.6 [ios.base.callback] |
register_callback can fail |
No |
3 |
|
2808 |
New |
27.5.4.2 [fpos.operations] |
Requirements for fpos and stateT |
No |
4 |
|
2832 |
New |
27.5.4.2 [fpos.operations] |
§[fpos.operations] strange requirement for P(i) |
No |
3 |
|
2214 |
Open |
27.5.5.2 [basic.ios.cons] |
Clarify basic_ios::init call restrictions |
Yes |
4 |
|
2504 |
New |
27.6.3 [streambuf] |
basic_streambuf is not an abstract class |
No |
3 |
|
2349 |
Open |
27.7.4.2.1 [istream.formatted.reqmts] |
Clarify input/output function rethrow behavior |
Yes |
3 |
|
2499 |
Open |
27.7.4.2.3 [istream.extractors] |
operator>>(basic_istream&, CharT*) makes it hard to avoid buffer overflows |
Yes |
2 |
|
2243 |
New |
27.7.4.3 [istream.unformatted] |
istream::putback problem |
No |
3 |
|
2498 |
New |
27.7.4.5 [istream.rvalue] |
operator>>(basic_istream&&, T&&) returns basic_istream&, but should probably return
basic_istream&& |
No |
3 |
|
2342 |
New |
27.7.5.1 [ostream] |
User conversion to wchar_t const* or to wchar_t not invoked for operator<< |
Yes |
4 |
|
2497 |
New |
27.7.5.1.3 [ostream::sentry] |
Use of uncaught_exception() |
No |
3 |
|
1203 |
LEWG |
27.7.5.5 [ostream.rvalue] |
More useful rvalue stream insertion |
Yes |
|
|
2286 |
New |
27.8.2.4 [stringbuf.virtuals] |
stringbuf::underflow() underspecified |
Yes |
4 |
|
2121 |
New |
27.8.5.1 [stringstream.cons] |
app for string streams |
No |
3 |
|
2943 |
New |
27.9.2.3 [filebuf.members] |
Problematic specification of the wide version of basic_filebuf::open |
No |
|
|
1150 |
LEWG |
27.9.5 [fstream] |
wchar_t, char16_t and char32_t filenames |
No |
|
|
2965 |
New |
27.10.9.1 [filesystem_error.members] |
Non-existing path::native_string() in filesystem_error::what() specification |
Yes |
|
|
2956 |
New |
27.10.15.2 [fs.op.canonical] |
filesystem::canonical() still defined in terms of absolute(p, base) |
No |
|
|
2682 |
Open |
27.10.15.3 [fs.op.copy] |
filesystem::copy() won't create a symlink to a directory |
Yes |
2 |
|
2849 |
New |
27.10.15.4 [fs.op.copy_file] |
Why does !is_regular_file(from) cause copy_file to report a "file already exists" error? |
Yes |
2 |
|
2935 |
New |
27.10.15.6 [fs.op.create_directories] |
What should create_directories do when p already exists but is not a directory? |
Yes |
|
|
2937 |
Tentatively Ready |
27.10.15.12 [fs.op.equivalent] |
Is equivalent("existing_thing", "not_existing_thing") an error? |
Yes |
0 |
|
2816 |
New |
27.10.15.33 [fs.op.resize_file] |
resize_file has impossible postcondition |
No |
3 |
|
Issue |
Status |
Section |
Title |
Proposed Resolution |
Priority |
Duplicates |
2941 |
New |
30.2.4 [thread.req.timing] |
§[thread.req.timing] wording should apply to both member and namespace-level functions |
Yes |
|
|
2819 |
New |
30.2.5 [thread.req.lockable] |
Unspecified Return type: elements |
No |
3 |
|
1484 |
LEWG |
30.3.2 [thread.thread.class] |
Need a way to join a thread with a timeout |
No |
|
|
1488 |
LEWG |
30.4 [thread.mutex] |
Improve interoperability between the C++0x and C1x threads APIs |
No |
|
|
936 |
LEWG |
30.4.3 [thread.mutex.requirements] |
Mutex type overspecified |
No |
|
961 |
961 |
LEWG |
30.4.3 [thread.mutex.requirements] |
Various threading bugs #11 |
No |
|
936 |
1493 |
LEWG |
30.4.3 [thread.mutex.requirements] |
Add mutex, recursive_mutex, is_locked function |
No |
|
|
2363 |
Open |
30.4.3.5.1 [thread.sharedtimedmutex.class] |
Defect in 30.4.1.4.1 [thread.sharedtimedmutex.class] |
Yes |
2 |
|
2731 |
New |
30.4.4.1 [thread.lock.guard] |
Existence of lock_guard<MutexTypes...>::mutex_type typedef unclear |
Yes |
3 |
|
1499 |
LEWG |
30.5 [thread.condition] |
Condition variables preclude wakeup optimization |
No |
|
|
2530 |
Open |
30.6.5 [futures.state] |
Clarify observable side effects of releasing a shared state |
No |
3 |
|
2412 |
Review |
30.6.6 [futures.promise] |
promise::set_value() and promise::get_future() should not race |
Yes |
|
|
2532 |
Open |
30.6.6 [futures.promise] |
Satisfying a promise at thread exit |
Yes |
3 |
|
2095 |
LEWG |
30.6.6 [futures.promise] |
promise and packaged_task missing constructors needed for uses-allocator construction |
Yes |
4 |
|
2799 |
New |
30.6.8 [futures.shared_future] |
noexcept-specifications in shared_future |
Yes |
2 |
|
2856 |
New |
30.6.9 [futures.async] |
std::async should be marked as [[nodiscard]] |
No |
2 |
|
2202 |
Deferred |
30.6.9 [futures.async] |
Missing allocator support by async |
No |
4 |
|
2976 |
New |
30.6.10 [futures.task] |
Dangling uses_allocator specialization for packaged_task |
Yes |
|
|