I suspect this is a remnant of the times when we were not comfortable
using Clang's C++11/14 extensions everywhere, but now we do, so we can
use _BoolConstant instead and get rid of the macro.
Details
Details
- Reviewers
jloser - Group Reviewers
Restricted Project - Commits
- rGf900f7025c7b: [libc++] Remove the _LIBCPP_BOOL_CONSTANT macro
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This seems pretty uncontroversial, so I'll ship this if CI is green unless there is discussion by Friday.
libcxx/include/exception | ||
---|---|---|
303 | This previously was public _LIBCPP_BOOL_CONSTANT, now it's a plain _BoolConstant - is the lost public keyword relevant here or not? |
libcxx/include/exception | ||
---|---|---|
303 | Not really, since it's a struct so it's public by default. The usual convention in metaprogramming is to omit the public and use structs all the time. |
This previously was public _LIBCPP_BOOL_CONSTANT, now it's a plain _BoolConstant - is the lost public keyword relevant here or not?