Date: Sun, 8 Dec 2019 13:02:15 +0000
As long as range-algorithms are not parallelizable (which according to the latest draft they aren’t), declaring iterator-based algorithms done is IMHO a bad idea…
From: Std-Proposals <std-proposals-bounces_at_[hidden]> On Behalf Of Domen Vrankar via Std-Proposals
Sent: Wednesday, December 4, 2019 10:46 AM
To: std-proposals_at_lists.isocpp.org
Cc: Domen Vrankar <domen.vrankar_at_[hidden]>
Subject: Re: [std-proposals] Should we have std::inplace_transform?
Just my opinion but I'd say that any algorithm extensions suhould build on top of ranges (composibility) and that current algorithms should be left as they are.
From: Std-Proposals <std-proposals-bounces_at_[hidden]> On Behalf Of Domen Vrankar via Std-Proposals
Sent: Wednesday, December 4, 2019 10:46 AM
To: std-proposals_at_lists.isocpp.org
Cc: Domen Vrankar <domen.vrankar_at_[hidden]>
Subject: Re: [std-proposals] Should we have std::inplace_transform?
Just my opinion but I'd say that any algorithm extensions suhould build on top of ranges (composibility) and that current algorithms should be left as they are.
Received on 2019-12-08 07:04:42