Issue 3302: Range adaptor objects keys and values are unspecified

Title: Range adaptor objects keys and values are unspecified
Status: c++20
Section: [ranges.syn]
Submitter: Michel Morin

Created on 2019-10-04.00:00:00 last changed 45 months ago

Messages

Date: 2019-11-07.08:57:59

Proposed resolution:

This wording is relative to N4830.

Modify [ranges.syn], header <ranges> synopsis, as indicated:

namespace std::ranges {
  […]
  
  template<class R>
    using keys_view = elements_view<all_view<R>, 0>;
  template<class R>
    using values_view = elements_view<all_view<R>, 1>;
  namespace views {
    template<size_t N>
      inline constexpr unspecified elements = unspecified;
    inline constexpr autounspecified keys = elements<0>unspecified;
    inline constexpr autounspecified values = elements<1>unspecified;
  }  
}
[…]

msg10721 (view)

Date: 2019-11-07.08:57:59

[ 2019-11 Wednesday night issue processing in Belfast. ]

Status to Ready.

msg10694 (view)

Date: 2019-10-31.00:00:00

[ 2019-10-31 Issue Prioritization ]

Priority to 1 after reflector discussion.

msg10693 (view)

Date: 2019-10-12.15:50:12

This issue was submitted as editorial issue cplusplus/draft#3231 but had been classified as non-editorial.

keys and values are listed in [ranges.syn], but not specified. It seems that P1035R7 forgot to specify them (as elements<0> and elements<1>).

History
Date	User	Action	Args
2021-02-25 10:48:01	admin	set	status: wp -> c++20
2020-02-24 16:02:59	admin	set	status: voting -> wp
2020-01-17 04:54:50	admin	set	status: ready -> voting
2019-11-07 08:57:59	admin	set	messages: + msg10793
2019-11-07 08:57:59	admin	set	status: new -> ready
2019-10-31 19:35:45	admin	set	messages: + msg10721
2019-10-12 11:16:44	admin	set	messages: + msg10694
2019-10-04 00:00:00	admin	create