std::experi...llyOrdered,(3)
πΈ std::experi...llyOrdered,(3) πΈ
okay bestie, this is the std::experi...llyOrdered,(3) manual page from the C++ Standard Libary β yes, the header spells it like that, no cap π β and it's all about the ranges TS concepts StrictTotallyOrdered and StrictTotallyOrderedWith from <experimental/ranges/concepts>. section 3 energy, concept girlie vibes, let's go π.
π NAME π
the NAME line is literally:
std::experimental::ranges::StrictTotallyOrdered, - std::experimental::ranges::StrictTotallyOrdered,
trailing comma and all. she's iconic, she's a little extra, she's the strict totally ordered concept from the ranges TS π¦.
β¨ Synopsis β¨
Defined in header <experimental/ranges/concepts>
template< class T >
concept bool StrictTotallyOrdered =
EqualityComparable<T> &&
requires(const std::remove_reference_t<T>& a,
const std::remove_reference_t<T>& b) { (1) (ranges TS)
{ a < b } -> Boolean&&;
{ a > b } -> Boolean&&;
{ a <= b } -> Boolean&&;
{ a >= b } -> Boolean&&;
};
template< class T, class U >
concept bool StrictTotallyOrderedWith =
StrictTotallyOrdered<T> &&
StrictTotallyOrdered<U> &&
CommonReference<
const std::remove_reference_t<T>&,
const std::remove_reference_t<U>&> &&
StrictTotallyOrdered<
ranges::common_reference_t<
const std::remove_reference_t<T>&,
const std::remove_reference_t<U>&>> &&
EqualityComparableWith<T, U> && (2) (ranges TS)
requires(const std::remove_reference_t<T>& t,
const std::remove_reference_t<U>& u) {
{ t < u } -> Boolean&&;
{ t > u } -> Boolean&&;
{ t <= u } -> Boolean&&;
{ t >= u } -> Boolean&&;
{ u < t } -> Boolean&&;
{ u > t } -> Boolean&&;
{ u <= t } -> Boolean&&;
{ u >= t } -> Boolean&&;
};
so here's the vibe: this synopsis is declaring two concepts from the ranges TS β StrictTotallyOrdered and StrictTotallyOrderedWith β and the numbered bits are doing the real explaining π
- The concept
StrictTotallyOrdered<T>specifies that the comparison operators==,!=,<,>,<=,>=onTyield results consistent with a strict total order onT.
StrictTotallyOrdered<T> is satisfied only if, given lvalues a, b and c of type const std::remove_reference_t<T>:
- Exactly one of
bool(a < b),bool(a > b)andbool(a == b)is true; - If
bool(a < b)andbool(b < c)are both true, thenbool(a < c)is true; bool(a > b) == bool(b < a)bool(a >= b) == !bool(a < b)bool(a <= b) == !bool(b < a)
- The concept
StrictTotallyOrderedWith<T, U>specifies that the comparison operators==,!=,<,>,<=,>=on (possibly mixed)TandUoperands yield results consistent with a strict total order. Comparing mixed operands yields results equivalent to comparing the operands converted to their common type.
Formally, StrictTotallyOrderedWith<T, U> is satisfied only if, given any lvalue t of type const std::remove_reference_t<T> and any lvalue u of type const std::remove_reference_t<U>, and let C be ranges::common_reference_t<const std::remove_reference_t<T>&, const std::remove_reference_t<U>&>:
bool(t < u) == bool(C(t) < C(u))bool(t > u) == bool(C(t) > C(u))bool(t <= u) == bool(C(t) <= C(u))bool(t >= u) == bool(C(t) >= C(u))bool(u < t) == bool(C(u) < C(t))bool(u > t) == bool(C(u) > C(t))bool(u <= t) == bool(C(u) <= C(t))bool(u >= t) == bool(C(u) >= C(t))
π Equality preservation π
An expression is equality preserving if it results in equal outputs given equal inputs.
- The inputs to an expression consist of its operands.
- The outputs of an expression consist of its result and all operands modified by the expression (if any).
Every expression required to be equality preserving is further required to be stable: two evaluations of such an expression with the same input objects must have equal outputs absent any explicit intervening modification of those input objects.
Unless noted otherwise, every expression used in a requires-expression is required to be equality preserving and stable, and the evaluation of the expression may only modify its non-constant operands. Operands that are constant must not be modified.
π§ Implicit expression variations π§
A requires-expression that uses an expression that is non-modifying for some constant lvalue operand also implicitly requires additional variations of that expression that accept a non-constant lvalue or (possibly constant) rvalue for the given operand unless such an expression variation is explicitly required with differing semantics. These implicit expression variations must meet the same semantic requirements of the declared expression. The extent to which an implementation validates the syntax of the variations is unspecified.
okay that's the whole page, bestie π«Άβ¨. the footer energy was: source/version http://cppreference.com, date 2024.06.10, and the page name std::experi...llyOrdered,(3). periodt π
π
π¦ where this page comes from
- nixpkgs unstable: stdman 2024.07.05
- opensuse-leap 16.0: stdman 2024.07.05-bp160.1.9 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms