Date: Fri, 25 Feb 2022 12:29:27 -0500
On Thu, Feb 24, 2022 at 11:27 PM Brook Milligan via Std-Proposals <
std-proposals_at_[hidden]> wrote:
>
> To my reading, documentation on the parallel STL algorithms (e.g.,
https://en.cppreference.com/w/cpp/algorithm/for_each)
> clearly indicate that the execution policy argument is taken with a
forwarding reference, which would seem to imply that
> either an lvalue or rvalue would be legitimate arguments. However, at
least libstdc++ shipped with gcc 10.3.0 requires
> only an lvalue as an argument. This seems like a defect in the library,
but perhaps I am misunderstanding.
It's a bug in pstl. I believe it was fixed by
https://reviews.llvm.org/D104492
–Arthur
std-proposals_at_[hidden]> wrote:
>
> To my reading, documentation on the parallel STL algorithms (e.g.,
https://en.cppreference.com/w/cpp/algorithm/for_each)
> clearly indicate that the execution policy argument is taken with a
forwarding reference, which would seem to imply that
> either an lvalue or rvalue would be legitimate arguments. However, at
least libstdc++ shipped with gcc 10.3.0 requires
> only an lvalue as an argument. This seems like a defect in the library,
but perhaps I am misunderstanding.
It's a bug in pstl. I believe it was fixed by
https://reviews.llvm.org/D104492
–Arthur
Received on 2022-02-25 17:29:39