The corresponding _LIBCPP_HAS_NO_SPACESHIP_OPERATOR macro was already
removed in commit c0f87e8382
Details
- Reviewers
Mordante ldionne philnik - Group Reviewers
Restricted Project - Commits
- rGcfefee87c28e: [libc++][NFC] Remove TEST_HAS_NO_SPACESHIP_OPERATOR
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM in essence, but I don't know what our stance on compiler support in the tests is. @ldionne do we have any schedule how long we support MSVC in the tests?
I think this should be fine -- MSVC definitely implements it nowadays and they use our test suite to run against their ToT compiler+stdlib (this is an assumption but it seems like a safe assumption to make).
@CaseyCarter Do you see a problem with this patch?
Please feel free to ship this if Casey's fine with it or if there's no answer by next Tuesday, I don't think this will cause any issues for them.
to my understanding, even before the removal of the TEST_HAS_NO_SPACESHIP_OPERATOR macro, the libc++ tests would not have worked on a compiler which doesn't support operator<=>.
We have other test cases (e.g. time/time.cal/time.cal.day/time.cal.day.nonmembers/comparisons.pass.cpp) which rely on the spaceship operator and are not guarded by this macro