The _Equal_memcmp_is_safe machinery in <xutility> determines when comparisons in algorithms can be optimized in terms of memcmp rather than using a simple loop. That machinery is activated in a very limited set of circumstances, currently only for iterators of pointer type using std::equal_to to compare elements of integral type. To provide parity for the ranges algorithms, this machinery needs to understand std::ranges::equal_to. To provide a better experience for ranges, this machinery also needs to activate for contiguous_iterators that aren't pointers.
The
_Equal_memcmp_is_safemachinery in<xutility>determines when comparisons in algorithms can be optimized in terms ofmemcmprather than using a simple loop. That machinery is activated in a very limited set of circumstances, currently only for iterators of pointer type usingstd::equal_toto compare elements of integral type. To provide parity for therangesalgorithms, this machinery needs to understandstd::ranges::equal_to. To provide a better experience forranges, this machinery also needs to activate forcontiguous_iterators that aren't pointers.