I checked this patch on my own build on RHEL 6. Regressions were OK.
Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
| include/clang/Basic/IdentifierTable.h | ||
|---|---|---|
| 34 | Not sure the whitespace adds any benefit here. | |
| 103 | Isn't the LLVM style to prefer the negation? Why did the infix operators not get space around them? | |
| include/clang/Frontend/ASTUnit.h | ||
| 52 | Not sure the whitespace is beneficial here. | |
| 928 | This is weirdly formatted. I think its fine to clang-format this line. | |
| include/clang/Lex/PreprocessorOptions.h | ||
| 22 | Don't think that the whitespace is beneficial here. | |
| include/clang/Basic/IdentifierTable.h | ||
|---|---|---|
| 103 | memcpy result is three state, so applying Boolean operator is not correct. | |
| include/clang/Lex/PreprocessorOptions.h | ||
| 22 | I wanted to make spacing consistent. Same in other places. Actually, Include What You Use recommended to include MemoryBuffer.h. MemoryBuffer is used in smart pointers, but I remember that I encountered problems in LLDB MSVC builds, where forward declaration was not enough for such usage. | |
| include/clang/Basic/IdentifierTable.h | ||
|---|---|---|
| 103 | What do you mean "applying Boolean operator is not correct"? The value zero (for integral, floating-point, and unscoped enumeration) and the null pointer and the null pointer-to-member values become false. All other values become true. Seems good to me? | |
| include/clang/Lex/PreprocessorOptions.h | ||
| 22 | I think in a recent review you mentioned "empty lines make code more readable for large namespaces", which does not seem to be the case here? | |
Not sure the whitespace adds any benefit here.