D131234 marked the ranges papers as complete, but it didn't set the
feature-test macro.
Details
Details
- Reviewers
ldionne var-const - Group Reviewers
Restricted Project - Commits
- rG195287d90afb: [libc++][ranges] Sets ranges feature-test macro.
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
LGTM, but let's have @var-const double-check that this is indeed what we want. I think it is.
Comment Actions
LGTM with one comment.
libcxx/test/std/language.support/support.limits/support.limits.general/algorithm.version.compile.pass.cpp | ||
---|---|---|
260 | Is this correct? Reading aloud, it seems to say when not defined ... is not defined. The exclamation mark looks unnecessary, and perhaps the first defined is unnecessary as well -- would it read better as should not be defined when _LIBCPP_HAS_NO_INCOMPLETE_RANGES is not defined? |
Comment Actions
Thanks for the reviews!
libcxx/test/std/language.support/support.limits/support.limits.general/algorithm.version.compile.pass.cpp | ||
---|---|---|
260 | I agree it looks weird and we could improve the wording. However I will do that in a followup. | |
libcxx/utils/generate_feature_test_macro_components.py | ||
984 | @var-const here the error is generated. |
libcxx/utils/generate_feature_test_macro_components.py | ||
---|---|---|
984 | Thanks for explaining! |
Is this correct? Reading aloud, it seems to say when not defined ... is not defined. The exclamation mark looks unnecessary, and perhaps the first defined is unnecessary as well -- would it read better as should not be defined when _LIBCPP_HAS_NO_INCOMPLETE_RANGES is not defined?