Date: Thu, 16 Jul 2026 12:35:09 +0000
Yes, that's one way to understand it. I had previously overlooked and missed this feature of ranges::to. Thank you for providing this important information.
________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Giuseppe D'Angelo via Std-Proposals <std-proposals_at_[hidden]>
Sent: Thursday, July 16, 2026 20:05
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Giuseppe D'Angelo <giuseppe.dangelo_at_[hidden]>
Subject: Re: [std-proposals] Proposal: ranges::reserve
On 16/07/2026 10:24, Yexuan Xiao via Std-Proposals wrote:
> I have realized that the second version I proposed is incorrect and the
> first version is correct, except for its name and the parameter.
Just to better understand, are you proposing to expose/standardize the
functionality currently "hidden" into ranges::to?
Specifically the reserveable-container machinery in
https://eel.is/c++draft/range.utility.conv#to-2.1.4
https://eel.is/c++draft/range.utility.conv#general-3
Thanks,
________________________________
From: Std-Proposals <std-proposals-bounces_at_[hidden]> on behalf of Giuseppe D'Angelo via Std-Proposals <std-proposals_at_[hidden]>
Sent: Thursday, July 16, 2026 20:05
To: std-proposals_at_[hidden] <std-proposals_at_[hidden]>
Cc: Giuseppe D'Angelo <giuseppe.dangelo_at_[hidden]>
Subject: Re: [std-proposals] Proposal: ranges::reserve
On 16/07/2026 10:24, Yexuan Xiao via Std-Proposals wrote:
> I have realized that the second version I proposed is incorrect and the
> first version is correct, except for its name and the parameter.
Just to better understand, are you proposing to expose/standardize the
functionality currently "hidden" into ranges::to?
Specifically the reserveable-container machinery in
https://eel.is/c++draft/range.utility.conv#to-2.1.4
https://eel.is/c++draft/range.utility.conv#general-3
Thanks,
-- Giuseppe D'Angelo
Received on 2026-07-16 12:35:20
