C++ Standard Library Issues List (Revision D126)

Index by Section

Reference ISO/IEC IS 14882:2024(E)

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

Index by Section

(view only non-Ready open issues)

Revised 2026-05-30 at 15:31:21 UTC

Section 17 (3 issues)

(view only non-Ready open issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4182⁽ⁱ⁾	Ready	17.2.3 [support.types.nullptr]	Definition of `NULL` is too broad	Yes	3
4567⁽ⁱ⁾	Tentatively Ready	17.3.2 [version.syn]	Feature test macro value for `apply_result`, `is_applicable`	Yes
4531⁽ⁱ⁾	Tentatively Ready	17.3.2 [version.syn]	Should there be a feature-test macro update for constexpr `std::to_(w)string`?	Yes	2

Section 22 (1 issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4267⁽ⁱ⁾	Ready	22.4.4.2 [tuple.cnstr]	Uses-allocator construction is meaningless for tuple of references	Yes	3

Section 24 (3 issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4218⁽ⁱ⁾	Ready	24.5.3.5 [const.iterators.ops]	Constraint recursion in `basic_const_iterator`'s relational operators due to ADL + CWG 2369	Yes	2
4125⁽ⁱ⁾	Ready	24.5.4.2 [move.iterator]	`move_iterator`'s default constructor should be constrained	Yes	3
4385⁽ⁱ⁾	Ready	24.7 [iterator.range]	Including `<simd>` doesn't provide `std::begin/end`	Yes	3

Section 25 (3 issues)

(view only non-Ready open issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4577⁽ⁱ⁾	Ready	25.5.3 [view.interface]	Hardening `view_interface::operator[]`	Yes
4121⁽ⁱ⁾	Tentatively Ready	25.5.7.1 [range.utility.conv.general]	`ranges::to` constructs associative containers via `c.emplace(c.end(), *it)`	Yes	2
4249⁽ⁱ⁾	Ready	25.7.16.3 [range.lazy.split.outer]	The past end issue for `lazy_split_view`	Yes	2

Section 26 (1 issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4490⁽ⁱ⁾	Ready	26.2 [algorithms.requirements]	Allow calling `std::ranges::size` in ranges algorithms	Yes	3

Section 30 (1 issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4487⁽ⁱ⁾	Ready	30.3 [time.clock.req]	Is member `is_steady` of a Cpp17Clock type required to be usable in constant expressions?	Yes	3

Section 32 (3 issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4521⁽ⁱ⁾	Ready	32.5.4 [atomics.order]	Improve [atomics.order] p10 to have a consistent way with [intro.races]	Yes	4
3417⁽ⁱ⁾	Ready	32.5.8.2 [atomics.types.operations]	Missing `volatile` atomic deprecations	Yes	3
4158⁽ⁱ⁾	Ready	32.10.10.2 [futures.task.members]	`packaged_task::operator=` should abandon its shared state	Yes	3

Section 33 (4 issues)

(view only non-Ready open issues)

Issue	Status	Section	Title	Proposed Resolution	Priority	Duplicates
4579⁽ⁱ⁾	Tentatively Ready	33.9.12.12 [exec.when.all]	`make-state<Rcvr>::state-type::complete` uses `Env` which is not in scope	Yes
4568⁽ⁱ⁾	Tentatively Ready	33.9.12.18 [exec.spawn.future]	`std::execution::spawn_future` is mishandling dependent senders	Yes
4359⁽ⁱ⁾	Ready	33.13.1 [exec.as.awaitable]	`as_awaitable(expr, p)` does not define semantics of call if `p` is not an lvalue	Yes	2
4471⁽ⁱ⁾	Ready	33.13.4 [exec.inline.scheduler]	Remove test for `get_env noexcept`-ness from `inline_scheduler`	Yes	4