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

Created on 2023-08-27.00:00:00 last changed 12 months ago

Messages

Date: 2023-11-13.14:08:10

Proposed resolution:

This wording is relative to N4958.

  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>, <list>, <map>, <regex>, <set>, <span>, <string>, <string_view>, <unordered_map>, <unordered_set>, and <vector>.

Date: 2023-11-11.00:00:00

[ 2023-11-11 Approved at November 2023 meeting in Kona. Status changed: Voting → WP. ]

Date: 2023-11-15.00:00:00

[ 2023-11-02; Reflector poll ]

Set status to Tentatively Ready after nine votes in favour during reflector poll.

Date: 2023-08-27.00:00:00

It seems that [iterator.range] should also add <flat_foo> to the list as the latter provides a series of range access member functions such as begin/end.

History
Date User Action Args
2023-11-13 14:08:10adminsetmessages: + msg13853
2023-11-13 14:08:10adminsetstatus: voting -> wp
2023-11-07 21:41:54adminsetstatus: ready -> voting
2023-11-03 18:08:35adminsetmessages: + msg13813
2023-11-03 18:08:35adminsetstatus: new -> ready
2023-10-02 14:34:41adminsetmessages: + msg13741
2023-08-27 00:00:00admincreate