Can A and B be compared in the injected order Ord, at compile time? Both must expose ::value of one carrier type T that is IsPosetal under Ord's resolved relation, and that relation must be default-constructible and constexpr-callable on those values. A registered-but-runtime-only or stateful order therefore fails this guard and the glb/lub collapse stays inactive (fail-closed) rather than hard-erroring. More...

Concept definition

template<typename A, typename B, typename Ord>
concept dedekind::category::OrderComparable = 
    requires {
      A::value;
      B::value;
    } &&
    std::same_as<std::remove_cvref_t<decltype(A::value)>,
                 std::remove_cvref_t<decltype(B::value)>> &&
    IsPosetal<std::remove_cvref_t<decltype(A::value)>,
              resolved_order_t<std::remove_cvref_t<decltype(A::value)>, Ord>> &&
    std::default_initializable<
        resolved_order_t<std::remove_cvref_t<decltype(A::value)>, Ord>> &&
    requires {
      {
        resolved_order_t<std::remove_cvref_t<decltype(A::value)>, Ord>{}(
            A::value, B::value)
      } -> std::convertible_to<bool>;
      
      
      typename std::bool_constant<(
          resolved_order_t<std::remove_cvref_t<decltype(A::value)>, Ord>{}(
              A::value, B::value),
          true)>;
    }

Detailed Description

Can A and B be compared in the injected order Ord, at compile time? Both must expose ::value of one carrier type T that is IsPosetal under Ord's resolved relation, and that relation must be default-constructible and constexpr-callable on those values. A registered-but-runtime-only or stateful order therefore fails this guard and the glb/lub collapse stays inactive (fail-closed) rather than hard-erroring.