Title
Including <stacktrace> doesn't provide `std::begin/end`
Status
open
Section
[iterator.range]
Submitter
Hewill Kang

Created on 2025-09-27.00:00:00 last changed 5 days ago

Messages

Date: 2025-10-07.09:38:24

Proposed resolution:

This wording is relative to N5014.

  1. Modify [iterator.range] as indicated:

    -1- In addition to being available via inclusion of the <iterator> header, the function templates in [iterator.range] are available when any of the following headers are included: <array>, <deque>, <flat_map>, <flat_set>, <forward_list>, <hive>, <inplace_vector>, <list>, <map>, <regex>, <set>, <span>, <stacktrace>, <string>, <string_view>, <unordered_map>, <unordered_set>, and <vector>.

Date: 2025-10-15.00:00:00

[ 2025-10-07; Reflector poll ]

Approved as Tentatively Ready, but this is a duplicate of 3625 which will be resolved by P3016R6. So move Status New → Open.

Date: 2025-09-27.00:00:00

`basic_stacktrace` is explicitly specified as a reversible container, an allocator-aware container, and a const-qualified sequence container, with members `begin`/`end`, `rbegin`/`rend`, `cbegin`/`cend`, `crbegin`/`crend`, `empty`, `size`, etc.

Thus, it's worth making the corresponding free functions available when introducing <stacktrace>, just like other containers.

History
Date User Action Args
2025-10-07 09:38:24adminsetmessages: + msg15128
2025-10-07 09:38:24adminsetstatus: new -> open
2025-09-27 17:39:53adminsetmessages: + msg15092
2025-09-27 00:00:00admincreate