This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of WP status.
Section: 23.3.4 [string.view.comparison] Status: WP Submitter: Jonathan Wakely Opened: 2020-04-19 Last modified: 2020-11-09
View all issues with WP status.
It's not clear what happens if a program-defined character traits type defines comparison_category as a synonym for void, or some other bogus type.
Discussion on the LWG reflector settled on making it ill-formed at the point of use.
[2020-07-17; Moved to Ready in telecon]
[2020-11-09 Approved In November virtual meeting. Status changed: Ready → WP.]
This wording is relative to N4861.
Modify 23.3.4 [string.view.comparison] by adding a new paragraph after p3:
As result of reflector discussion we decided to make a drive-by fix in p3 below.
template<class charT, class traits> constexpr see below operator<=>(basic_string_view<charT, traits> lhs, basic_string_view<charT, traits> rhs) noexcept;
-3- Let R denote the type traits::comparison_category if
it exists, otherwise R is weak_ordering.
-4- Returns: static_cast<R>(lhs.compare(rhs) <=> 0).