Title
No definition of "Stable" for copy algorithms
Status
c++14
Section
[algorithm.stable]
Submitter
Pablo Halpern

Created on 2011-03-24.00:00:00 last changed 122 months ago

Messages

Date: 2011-08-16.10:45:53

Proposed resolution:

This wording is relative to the FDIS.

  1. In [algorithm.stable] p. 1 change as indicated:

    When the requirements for an algorithm state that it is “stable” without further elaboration, it means:

    • For the sort algorithms the relative order of equivalent elements is preserved.
    • For the remove and copy algorithms the relative order of the elements that are not removed is preserved.
    • For the merge algorithms, for equivalent elements in the original two ranges, the elements from the first range precede the elements from the second range.
Date: 2011-08-16.10:45:53

[ Bloomington, 2011 ]

Move to Ready

Date: 2011-03-24.00:00:00

[algorithm.stable] specified the meaning of "stable" when applied to the different types of algorithms. The second bullet says:

— For the remove algorithms the relative order of the elements that are not removed is preserved.

There is no description of what "stable" means for copy algorithms, even though the term is applied to copy_if (and perhaps others now or in the future). Thus, copy_if is using the term without a precise definition.

History
Date User Action Args
2014-02-20 13:20:35adminsetstatus: wp -> c++14
2012-02-12 18:36:43adminsetstatus: voting -> wp
2012-02-09 04:07:48adminsetstatus: ready -> voting
2011-08-16 10:45:53adminsetmessages: + msg5836
2011-08-16 10:45:53adminsetstatus: new -> ready
2011-04-19 21:45:46adminsetmessages: + msg5717
2011-03-24 00:00:00admincreate