运算符的要求<恒定性在标准::stable_sort

Requirement of operator< constness in std::stable_sort

本文关键字:标准 stable sort 恒定性 lt 运算符      更新时间:2023-10-16

我对 std::sort 和 std::stable_sortoperator<const限定符的要求差异有点困惑。假设一个简单的结构:

#include <vector>
#include <algorithm>
struct Custom {
bool operator<(const Custom& custom) /* const */{
return true;
};
};

如果我们尝试编译并运行此代码,一切正常:

int main() {
std::vector<Custom> values(3);
std::sort(values.begin(), values.end());
return 0;
}

但是这段带有std::stable_sort的代码编译失败:

int main() {
std::vector<Custom> values(3);
std::sort(values.begin(), values.end());
return 0;
}

下面是错误堆栈跟踪:

In file included from /usr/include/c++/5/bits/stl_algobase.h:71:0,
from /usr/include/c++/5/bits/char_traits.h:39,
from /usr/include/c++/5/ios:40,
from /usr/include/c++/5/ostream:38,
from /usr/include/c++/5/iostream:39,
from temp.cpp:1:
/usr/include/c++/5/bits/predefined_ops.h: In instantiation of ‘bool __gnu_cxx::__ops::_Val_less_iter::operator()(_Value&, _Iterator) const [with _Value = const Custom; _Iterator = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >]’:
/usr/include/c++/5/bits/stl_algo.h:2050:14:   required from ‘_ForwardIterator std::__upper_bound(_ForwardIterator, _ForwardIterator, const _Tp&, _Compare) [with _ForwardIterator = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >; _Tp = Custom; _Compare = __gnu_cxx::__ops::_Val_less_iter]’
/usr/include/c++/5/bits/stl_algo.h:2522:26:   required from ‘void std::__merge_without_buffer(_BidirectionalIterator, _BidirectionalIterator, _BidirectionalIterator, _Distance, _Distance, _Compare) [with _BidirectionalIterator = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >; _Distance = long int; _Compare = __gnu_cxx::__ops::_Iter_less_iter]’
/usr/include/c++/5/bits/stl_algo.h:2782:34:   required from ‘void std::__inplace_stable_sort(_RandomAccessIterator, _RandomAccessIterator, _Compare) [with _RandomAccessIterator = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >; _Compare = __gnu_cxx::__ops::_Iter_less_iter]’
/usr/include/c++/5/bits/stl_algo.h:4863:28:   required from ‘void std::__stable_sort(_RandomAccessIterator, _RandomAccessIterator, _Compare) [with _RandomAccessIterator = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >; _Compare = __gnu_cxx::__ops::_Iter_less_iter]’
/usr/include/c++/5/bits/stl_algo.h:4897:36:   required from ‘void std::stable_sort(_RAIter, _RAIter) [with _RAIter = __gnu_cxx::__normal_iterator<Custom*, std::vector<Custom> >]’
temp.cpp:15:45:   required from here
/usr/include/c++/5/bits/predefined_ops.h:71:22: error: no match for ‘operator<’ (operand types are ‘const Custom’ and ‘Custom’)
{ return __val < *__it; }

所以我的问题是: 这仅仅是技术实现细节的结果,还是存在一些支持这种行为的客观论据?

[alg.sorting]/2Compare是一个函数对象类型 (20.9(。应用于类型Compare对象的函数调用操作的返回值,当上下文转换为bool(子句 4(时,如果调用的第一个参数小于第二个参数,则true,否则falseCompare comp用于假设排序关系的算法。假设comp不会通过取消引用的迭代器应用任何非常量函数。

[alg.sorting]/3对于所有需要Compare的算法,有一个版本使用operator<代替。也就是说,comp(*i, *j) != false默认为*i < *j != false.

[res.on.functions]/1在某些情况下(替换函数、处理程序函数、对用于实例化标准库模板组件的类型的操作(,C++标准库依赖于C++程序提供的组件。如果这些组件不符合其要求,则标准对实施没有要求。

强调我的。程序通过向标准库函数提供不符合函数要求的组件来表现出未定义的行为。

顺便说一句,clang拒绝std::sortstd::stable_sort.