C++ Standard Library Issues List (Revision R98)

Index by Status and Section

Reference ISO/IEC IS 14882:2011(E)

This document is the Index by Status and Section for the Library Active Issues List, Library Defect Reports List, and Library Closed Issues List.

Revised 2016-05-30 at 02:05:30 UTC

Ready (21 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2549 Ready 20.4.2.1 [tuple.cnstr] Tuple EXPLICIT constructor templates that take tuple parameters end up taking references to temporaries and will create dangling references Yes 2
2393 Ready 20.12.12.2 [func.wrap.func] std::function's Callable definition is broken Yes 2
2542 Ready 23.2.4 [associative.reqmts] Missing const requirements for associative containers Yes 1
2436 Ready 23.2.4 [associative.reqmts] Comparators for associative containers should always be CopyConstructible Yes 2
2550 Ready 23.2.5 [unord.req] Wording of unordered container's clear() method complexity Yes 2
2310 Ready 23.3.7.1 [array.overview] Public exposition only member in std::array Yes 4
2181 Ready 26.6.1.2 [rand.req.seedseq] Exceptions from seed sequence operations Yes 3
2328 Ready 27.7.2.6 [istream.rvalue] Rvalue stream extraction should use perfect forwarding Yes 3
2667 Ready 27.10.8.4.9 [path.decompose] path::root_directory() description is confusing Yes 0
2669 Ready 27.10.14.1 [rec.dir.itr.members] recursive_directory_iterator effects refers to non-existent functions Yes 0
2671 Ready 27.10.15.3 [fs.op.copy] Errors in Copy Yes 0
2673 Ready 27.10.15.33 [fs.op.status] status() effects cannot be implemented as specified Yes 0
2670 Ready 27.10.15.36 [fs.op.system_complete] system_complete refers to undefined variable 'base' Yes 0
2441 Ready 29.5 [atomics.types.generic] Exact-width atomic typedefs should be provided Yes 0
2426 Ready 29.6.5 [atomics.types.operations.req] Issue about compare_exchange Yes 1
2309 Ready 30.4.1.2 [thread.mutex.requirements.mutex] mutex::lock() should not throw device_or_resource_busy Yes 0
2555 Ready 5.3 [fund.ts.v2::optional.object] [fund.ts.v2] No handling for over-aligned types in optional Yes 0
2451 Ready 5.3 [fund.ts.v2::optional.object] [fund.ts.v2] optional<T> should 'forward' T's implicit conversions Yes
2573 Ready 8.2.1 [fund.ts.v2::memory.smartptr.shared] [fund.ts.v2] std::hash<std::experimental::shared_ptr<T>> does not work for arrays Yes 0
2551 Ready 8.2.1.1 [fund.ts.v2::memory.smartptr.shared.const] [fund.ts.v2] "Exception safety" cleanup in library fundamentals required Yes 0
2516 Ready 8.12.1 [fund.ts.v2::memory.observer.ptr.overview] [fund.ts.v2] Public "exposition only" members in observer_ptr Yes 2

Tentatively Ready (12 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2710 Tentatively Ready 17.5.1.4 [structure.specifications] "Effects: Equivalent to ..." doesn't count "Synchronization:" as determined semantics Yes 0
2685 Tentatively Ready 20.10.2.2.1 [util.smartptr.shared.const] shared_ptr deleters must not not throw on move construction Yes 0
2698 Tentatively Ready 23.2.3 [sequence.reqmts] Effect of assign() on iterators/pointers/references Yes 0
2596 Tentatively Ready 23.3.11.4 [vector.data] vector::data() should use addressof Yes 0
2684 Tentatively Ready 23.6.5 [priority.queue] priority_queue lacking comparator typedef Yes 0
2689 Tentatively Ready 25.4.1 [alg.copy] Parallel versions of std::copy and std::move shouldn't be in order Yes 0
2688 Tentatively Ready 25.5.8 [alg.clamp] clamp misses preconditions and has extraneous condition on result Yes 0
2707 Tentatively Ready 27.10.8 [class.path] path construction and assignment should have "string_type&&" overloads Yes 0
2674 Tentatively Ready 27.10.8.5 [path.itr] Bidirectional iterator requirement on path::iterator is very expensive Yes 2
2706 Tentatively Ready 27.10.14 [class.rec.dir.itr] Error reporting for recursive_directory_iterator::pop() is under-specified Yes 0
2683 Tentatively Ready 27.10.15.3 [fs.op.copy] filesystem::copy() says "no effects" Yes 0
2509 Tentatively Ready 6.4 [fund.ts.v2::any.nonmembers] [fund.ts.v2] any_cast doesn't work with rvalue reference targets and cannot move with a value target Yes 2