The three-way comparison operator, written as , compares two objects and returns a result that represents less than, equal to, or greater than. In modern C++, it can replace several separate relational operators and help the compiler synthesize consistent comparison behavior from a single definition.
What the three-way comparison operator does
The three-way comparison operator, <=>, is a compact way to compare two values and produce a single ordering result: less than, equal to, or greater than. In modern C++, it can reduce duplicated comparison code and help keep ordering logic consistent.
Its main value is not just brevity. By centralising comparison into one operation, it reduces the chance that separate <, >, and == implementations drift apart or disagree on edge cases.
How C++ uses three-way comparison
In C++, <=> is commonly called the spaceship operator. It can be declared directly for a type, and the compiler may use it to generate the usual relational operators automatically when the comparison category supports that synthesis.
C++ does not treat every comparison as identical. The return type can express different ordering strengths, such as a full ordering or a partial ordering, which matters when values such as floating-point numbers can compare ambiguously because of NaN behavior.
This makes the operator more than syntactic sugar. It is part of the language’s comparison model, helping developers define a type’s ordering semantics once instead of repeating the same intent across multiple operators.
Why it improves consistency and readability
A single comparison definition is easier to reason about than a set of hand-written relational operators. When a type has many fields, developers can compare members in priority order and rely on the result to drive the rest of the ordering behavior.
That consistency is especially useful in sorting, ordered containers, and any code that depends on stable object ordering. If different comparison operators are implemented independently, subtle mismatches can cause incorrect container behavior or confusing results in tests.
Modern C++ also supports defaulted three-way comparison for suitable classes, which can save boilerplate when the natural member-wise ordering matches the intended semantics.
Common limitations and semantic choices
The three-way comparison operator is not always the right answer. Some types do not have a natural total order, and some domains need comparison rules that are intentionally selective, approximate, or domain-specific rather than fully lexicographic.
It also requires careful thought about what “equal” and “ordered” should mean for the type. If a class contains floating-point members, pointer-like members, or fields with business-specific equivalence rules, the comparison category and implementation must reflect those semantics accurately.
In practice, <=> is most valuable when a type really does have an ordering relationship that should be expressed clearly and consistently, not when comparison is only an incidental convenience.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on September 24, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
