C++ Standard Library Issues List (Revision D112)

Index by Section

Reference ISO/IEC IS 14882:2011(E)

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

Index by Section

(view only non-Ready open issues)

Revised 2018-07-08 at 15:00:35 UTC

Section 16 (1 issues)

(view only non-Ready open issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
3122 Tentatively Ready 16.3.1 [support.limits.general] __cpp_lib_chrono_udls was accidentally dropped Yes 0

Section 19 (3 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
3054 Ready 19.10.11.4 [uninitialized.copy] uninitialized_copy appears to not be able to meet its exception-safety guarantee Yes 2
2996 Ready 19.11.3 [util.smartptr.shared] Missing rvalue overloads for shared_ptr operations Yes
3116 Ready 19.13.4 [allocator.adaptor.members] OUTERMOST_ALLOC_TRAITS needs remove_reference_t Yes 0

Section 27 (3 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2995 Ready 27.8.2.1 [stringbuf.cons] basic_stringbuf default constructor forbids it from using SSO capacity Yes 3
2936 Ready 27.11.7.4.8 [fs.path.compare] Path comparison is defined in terms of the generic format Yes 2
2682 Ready 27.11.14.3 [fs.op.copy] filesystem::copy() won't create a symlink to a directory Yes 2

Section 28 (2 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2183 Ready 28.10.1 [re.results.const] Muddled allocator requirements for match_results constructors Yes 3
2184 Ready 28.10.1 [re.results.const] Muddled allocator requirements for match_results assignments Yes 3

Section 30 (1 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2412 Ready 30.6.6 [futures.promise] promise::set_value() and promise::get_future() should not race Yes 3

Section concurr.ts 99 (1 issues)

Issue Status Section Title Proposed Resolution Priority Duplicates
2697 Ready 99 [concurr.ts::futures.unique_future] [concurr.ts] Behavior of future/shared_future unwrapping constructor when given an invalid future Yes 2