Fairly straightforward: these tests were written without an implementation of <=>, and they're incorrectly testing that 0 <=> foo has the behavior that is required for foo <=> 0.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
I'm a bit concerned about the TEST_HAS_NO_SPACESHIP_OPERATOR and how it tracks with _LIBCPP_HAS_NO_SPACESHIP_OPERATOR, but I'm not going to hold this up for that.
Comment Actions
Same. I tried to convince the compiler guys to define a feature-test macro, but they're paranoid about doing so before it's in the standard. We can clean this up when that happens.