Improving consistency of include guards #308
cflaviu
started this conversation in
Ideas and RFCs
Replies: 1 comment 3 replies
-
The latter is preferred and should be used in new code, as far as I understand. +1 on making this consistent (clang-tidy rules perhaps?) |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The include guards in project's headers are either classic #ifndef-#define-#endif guard or #pragma once. Only one type of include guard should be used.
Beta Was this translation helpful? Give feedback.
All reactions