-
```
(extracted from issue #163)
--
../hc/hc.cpp:1154:24: warning:
__gnu_cxx::__alloc_traits::value_type is defined in , which isn't directly
#included.
../hc/hc.cpp:1215:31: warning:
__gnu_cxx::__…
-
```
(extracted from issue #163)
--
../hc/hc.cpp:1154:24: warning:
__gnu_cxx::__alloc_traits::value_type is defined in , which isn't directly
#included.
../hc/hc.cpp:1215:31: warning:
__gnu_cxx::__…
-
```
(extracted from issue #163)
--
../hc/hc.cpp:1154:24: warning:
__gnu_cxx::__alloc_traits::value_type is defined in , which isn't directly
#included.
../hc/hc.cpp:1215:31: warning:
__gnu_cxx::__…
-
```
The mapping syntax supports a regex expression for the first entry of the
mapping. It would be nice if this could be extended to also be supported for
the 3rd entry(=2nd include). This would be …
-
```
The mapping syntax supports a regex expression for the first entry of the
mapping. It would be nice if this could be extended to also be supported for
the 3rd entry(=2nd include). This would be …
-
```
The mapping syntax supports a regex expression for the first entry of the
mapping. It would be nice if this could be extended to also be supported for
the 3rd entry(=2nd include). This would be …
-
Originally reported on Google Code with ID 48
```
Given a header file like this one:
#include
struct X {
void f(const SomeLargeClass &c) {
// lots of code here
}
};
... it would be great …
-
Maybe this is already covered and I just could not find the proper docs, sorry.
The current [IWYU rules of Google C++ style guide](https://google.github.io/styleguide/cppguide.html#Include_What_You…
-
When suggesting that GL/freeglut.h be replaced with freeglut_std and freeglut_ext.h, the suggested order is alphabetical, resulting in:
```
#include // for glutSetOption, glutLeaveMainL…
-
For example, libncurses5-dev is needed on (but wasn't installed on my Ubuntu machine).
How hard would it be to maintain a minimal-but-exhaustive list of things that the build needs? In theory such …
bcsgh updated
4 years ago