This is an archive of the discontinued LLVM Phabricator instance.

[libc++][NFC] Add TEST_HAS_NO_INCOMPLETE_RANGES.
ClosedPublic

Authored by Mordante on Mar 12 2022, 3:23 AM.

Details

Reviewers
ldionne
Group Reviewers
Restricted Project
Commits
rGe72cedcb0119: [libc++][NFC] Add TEST_HAS_NO_INCOMPLETE_RANGES.
Summary

This avoids using an libc++ internal macro in our tests.

Diff Detail

Event Timeline

Mordante created this revision.Mar 12 2022, 3:23 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 12 2022, 3:23 AM
Mordante requested review of this revision.Mar 12 2022, 3:23 AM
Herald added a project: Restricted Project. · View Herald TranscriptMar 12 2022, 3:23 AM
Herald added a reviewer: Restricted Project. · View Herald Transcript

Wouldn't the easier option be to add // UNSUPPORTED: has-no-incomplete-ranges? It seems a bit overkill to me to add a new macro for a single test.

Wouldn't the easier option be to add // UNSUPPORTED: has-no-incomplete-ranges? It seems a bit overkill to me to add a new macro for a single test.

I've considered that, but that would disable the entire test. Since the macro will be removed at some point I prefer to do it like this.
There are some other single occurrence macros where I want to discuss what the best approach will be. But I'll bring these macros up on Discord in the near future.

You said it yourself: The macro will be removed. We don't run any CI with _LIBCPP_HAS_NO_INCOMPLETE_RANGES, do we? If not I see no reason not do disable the entire test. It will only be disabled for those who don't ship ranges currently. I guess we should ask @ldionne what he thinks.

ldionne accepted this revision.Mar 15 2022, 7:14 PM

You said it yourself: The macro will be removed. We don't run any CI with _LIBCPP_HAS_NO_INCOMPLETE_RANGES, do we? If not I see no reason not do disable the entire test. It will only be disabled for those who don't ship ranges currently. I guess we should ask @ldionne what he thinks.

We do run CI with HAS_NO_INCOMPLETE_RANGES in the no-experimental CI job. Furthermore, that configuration is actually the default that we ship -- in other words, as far as users are concerned, they only see the library with HAS_NO_INCOMPLETE_RANGES, so it's important to test it if we can (until we can get rid of it entirely).

This revision is now accepted and ready to land.Mar 15 2022, 7:14 PM
This revision was automatically updated to reflect the committed changes.