3874. Rename __cpp_lib_ranges_to_container to __cpp_lib_ranges_to

Section: 17.3.2 [version.syn] Status: NAD Submitter: Hewill Kang Opened: 2023-02-05 Last modified: 2023-02-08

Priority: Not Prioritized

View other active issues in [version.syn].

View all other issues in [version.syn].

View all issues with NAD status.

Discussion:

LWG 3785 enables ranges::to to construct a non-range object from a range, confirming that this is the intended part of the original design.

However, the feature test macro for ranges::to is still named __cpp_lib_ranges_to_container, where the "container" part seems confusing to users.

[Issaquah 2023-02-08 Status changed: New → NAD.]

No consensus to change anything. The macro name is just a unique identifier, it doesn't have to be a precise description of the feature.

Proposed resolution:

This wording is relative to N4928.

1. Modify 17.3.2 [version.syn], header <version> synopsis, as indicated:

   […]
   #define __cpp_lib_ranges_stride                     202207L // also in <ranges>
   #define __cpp_lib_ranges_to_container               202202L // also in <ranges>
   #define __cpp_lib_ranges_zip                        202110L // also in <ranges>, <tuple>, <utility>
   […]