Title
Parallel algorithms with constexpr specifier
Status
c++17
Section
[algorithms.general]
Submitter
Jonathan Wakely

Created on 2016-06-21.00:00:00 last changed 81 months ago

Messages

Date: 2016-06-27.16:42:33

Proposed resolution:

This wording is relative to N4594.

  1. Change the <algorithm> header synopsis, [algorithms.general], as indicated, to remove "constexpr" from the six {min,max,minmax}_element overloads with an ExecutionPolicy argument:

    namespace std {
    
    […]
    // 25.5.7, minimum and maximum:
    […]
    template<class ExecutionPolicy, class ForwardIterator>
      constexpr ForwardIterator min_element(ExecutionPolicy&& exec, // see 25.2.5
                                            ForwardIterator first, ForwardIterator last);
    template<class ExecutionPolicy, class ForwardIterator, class Compare>
      constexpr ForwardIterator min_element(ExecutionPolicy&& exec, // see 25.2.5
                                            ForwardIterator first, ForwardIterator last,
                                            Compare comp);
    […]
    template<class ExecutionPolicy, class ForwardIterator>
      constexpr ForwardIterator max_element(ExecutionPolicy&& exec, // see 25.2.5
                                            ForwardIterator first, ForwardIterator last);
    template<class ExecutionPolicy, class ForwardIterator, class Compare>
      constexpr ForwardIterator max_element(ExecutionPolicy&& exec, // see 25.2.5
                                            ForwardIterator first, ForwardIterator last,
                                            Compare comp);
    […]
    template<class ExecutionPolicy, class ForwardIterator>
      constexpr pair<ForwardIterator, ForwardIterator>
        minmax_element(ExecutionPolicy&& exec, // see 25.2.5
                       ForwardIterator first, ForwardIterator last);
    template<class ExecutionPolicy, class ForwardIterator, class Compare>
      constexpr pair<ForwardIterator, ForwardIterator>
        minmax_element(ExecutionPolicy&& exec, // see 25.2.5
                       ForwardIterator first, ForwardIterator last, Compare comp);
    […]
    }
    
Date: 2016-06-27.16:42:33

[ 2016-06 Oulu ]

Moved to P0/Ready during issues prioritization.

Friday: status to Immediate

Date: 2016-06-21.00:00:00

In LEWG we noticed some parallel algorithms are constexpr. Jared said:

I think this is an oversight, and it also applies to std::max_element/std::minmax_element. To my knowledge, neither SG1 nor LWG ever explicitly considered whether a parallel algorithm should be constexpr. I think the assumption was that parallel algorithms would be regular old function templates without additional specifiers such as constexpr.

History
Date User Action Args
2017-07-30 20:15:43adminsetstatus: wp -> c++17
2016-06-28 13:14:43adminsetstatus: immediate -> wp
2016-06-27 16:42:33adminsetmessages: + msg8206
2016-06-27 16:42:33adminsetstatus: new -> immediate
2016-06-21 20:47:37adminsetmessages: + msg8194
2016-06-21 00:00:00admincreate