-
```
// a.h
struct Foo {};
// b.h
#include "a.h"
template int size() { return sizeof(T); }
template int foo() { return X + size(); }
// b.cc
#include "b.h"
// c.cc
#include "b.h"
int…
-
```cxx
// Foo.h
struct Foo {
};
```
```cxx
// Bar.h
#include
#include "Foo.h"
struct Bar {
std::unordered_map m;
};
```
```cxx
// Bar.cpp
#include "Bar.h"
```
IWYU (clang_1…
-
```
When reordering #includes, iwyu appears to use a case-sensitive ASCII
comparison. It would be nicer to be case-insensitive, and even better to also
sort punctuation before digits before letters.…
-
```
Boost often separates out implementation details into a "detail" folder, e.g.
. It would be nice if iwyu did not suggest
these detail headers.
```
Original issue reported on code.google.com by…
-
```
Boost often separates out implementation details into a "detail" folder, e.g.
. It would be nice if iwyu did not suggest
these detail headers.
```
Original issue reported on code.google.com by…
-
```
When reordering #includes, iwyu appears to use a case-sensitive ASCII
comparison. It would be nicer to be case-insensitive, and even better to also
sort punctuation before digits before letters.…
-
```
When reordering #includes, iwyu appears to use a case-sensitive ASCII
comparison. It would be nicer to be case-insensitive, and even better to also
sort punctuation before digits before letters.…
-
```
Boost often separates out implementation details into a "detail" folder, e.g.
. It would be nice if iwyu did not suggest
these detail headers.
```
Original issue reported on code.google.com by…
-
```
Given:
//simd.h:
#include // IWYU pragma: export
__m128 a;
//simd.imp:
[{ include: ["", "public", "", "public"] }]
I get:
simd.h should add these lines:
#include // for __m128
…
-
```
(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::__…