Title
The specification for adjacent_difference has baked-in sequential semantics
Status
resolved
Section
[adjacent.difference]
Submitter
United States

Created on 2017-02-03.00:00:00 last changed 85 months ago

Messages

Date: 2017-03-15.00:00:00

[ 2017-03-12, post-Kona ]

Resolved by P0467R2.

Date: 2017-02-15.00:00:00

[ 2017-02-25, Alisdair comments ]

Anthony Williams's paper on parallel algorithm complexity, p0574r0, includes wording that would resolve LWG issue 2919, and I suggest we defer initial triage to handling that paper.

Date: 2017-02-03.00:00:00
Addresses US 162

The specification for adjacent_difference has baked-in sequential semantics, in order to support reading/writing through input/output iterators. There should a second specification more amenable to parallelization for the overloads taking an execution policy.

Proposed change: Provide a specification for the overloads taking an execution policy this is more clearly suitable for parallel execution. (i.e., one that does not refer to an accumulated state.)

History
Date User Action Args
2017-03-12 23:04:12adminsetmessages: + msg9091
2017-03-12 23:04:12adminsetstatus: new -> resolved
2017-02-25 13:41:24adminsetmessages: + msg8999
2017-02-03 00:00:00admincreate