The macro TEST_HAS_NO_EXCEPTIONS seems to be defined very similar to _LIBCPP_NO_EXCEPTIONS, I'm thinking of getting rid of the former as the latter is more general (defined in __config).
I'm curious as to why the TEST_HAS_NO_EXCEPTIONS macro was introduced? Until very recently, we did not have any -fno-exceptions test runs AFAIK.
If readability is the reason for this macro, we can instead do:
#define TEST_HAS_NO_EXCEPTIONS _LIBCPP_NO_EXCEPTIONS
No functional changes.