-
This would be a more robust solution. `#pragma once` is fine for first-party code in a project, but for third party users, there will always be edge cases.
-
I'm not seeing any include guards in the project's internal headers.
Is there any particular reason there aren't any?
-
On a somewhat related subject to #66, we got a false positive today in [misc-include-cleaner](https://clang.llvm.org/extra/clang-tidy/checks/misc/include-cleaner.html)
Somebody removed 2 headers th…
-
Should use some kind of include guards, the issue is when headers are included multiple times or if they have circular dependencies.
Although the headers here are too simple to cause issues, it is …
-
Including a file multiple times should automatically guard against re-loading the same file multiple times. This is especially important with diamond dependencies.
Main.gravity
```swift
#include …
-
https://llvm.org/docs/CodingStandards.html#include-style
Immediately after the [header file comment](https://llvm.org/docs/CodingStandards.html#header-file-comment) (and include guards if working o…
-
```
compiling xAODJetReclustering
Making dependency for ReclusteredJetTrimmingTool.cxx
Making dependency for JetReclusteringTool.cxx
Making dependency for LinkDef.h
Making dependency for LinkDef.h
Mak…
-
:thought_balloon: I find that an include guard like “[`VINA_H`](https://github.com/ccsb-scripps/AutoDock-Vina/blob/d13f9e93e253573b01ffbb28cfd1e2dd26ff9002/src/lib/vina.h#L23 "Update candidate")” is t…
-
The `!include` meta command does what the name states - so far so good. However it does not check if a file has been included already and multiple `!include` statements for the same file lead to actua…
-
Include guards in C are named without any system. Lets set some convention for this and consider using `#pragma once` instead ifdefs.