-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add clang-tidy check for &&, || and ! instead of and, or and not #2569
ci: Add clang-tidy check for &&, || and ! instead of and, or and not #2569
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2569 +/- ##
==========================================
- Coverage 49.55% 49.54% -0.01%
==========================================
Files 472 472
Lines 26724 26719 -5
Branches 12318 12313 -5
==========================================
- Hits 13244 13239 -5
Misses 4748 4748
Partials 8732 8732
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Fixes are ready but I want to see the CI fail first. |
But why would we want to forbid |
As with everything, it's a matter of taste I find it very confusing, and it's bringing one of the worst parts of python syntax to C++. And the worst imo is having both styles in the same codebase. At the very least, we should then also switch the rest of the operators, like |
I also have a rather strong opinion of not using but more importantly I think it should be consistent across the codebase |
@andiwand We all have keyboards with keys for punctuation marks nowadays, right? 😅 |
Do we? 😆 But I agree, However, I actually would argue to keep at least if( !longVariableName ) vs. if( not longVariableName ) the latter one is better readable I think. |
Needed a few more fixes unfortunately, @andiwand. |
No description provided.