isocpp / isocpp/CppCoreGuidelines
Should alternative tokens be recommended?
Open
@gdr-at-ms is already working on this.
Since Nov 27, 2017.
- Dominant language
- CSS
- Stars
- 45.3k
- Forks
- 5.6k
- PR merge metrics
- No merged PRs in 30d
Description
Alternative tokens provide human-readable string names for certain operators.
For example:
if (x && y.empty()) {
}
Becomes:
if (x and y.empty()) {
}
I've always personally found these easier to read (perhaps influenced from Python background). As far as I understand these identifiers are proper keywords in C++. However, I am hesitant to use them because my impression is that it is not idiomatic to use them in C++.
Also, the bitwise operator names (bitand, bitor) feel like a bit of overkill compared to boolean ones.
Some options I feel could be considered:
- Guidelines don't mention alternative tokens (I couldn't find a mention in the current guidelines)
- Guidelines recommend no alternative tokens are used
- Guidelines recommend the boolean tokens (
and,or,not) - Guidelines recommend boolean and bitwise tokens (
and,or,not,bitand,bitor,and_eq, etc)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.