Diff Detail
Event Timeline
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 190–191 | I'd name the variable BB instead because BasicBlock is the name of a class in LLVM. | |
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 190–191 | that's why I don't like this convention :P | |
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 190–192 | We all take issue with some part of the coding style but it is important that we all stick to it. | |
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 190–192 | Yep, I hope my middle aproach with "BBblock" is similiar enough. Seriously name like BB for newbie like me doesn't give me any information more than 2 random letters | |
BB very frequently is BasicBlock and I is Instruction, typically in loops
for (... &BB : F) for (... &I : BB)
grep "&BB :" to see more examples. The variable name should really be BB to follow existing code conventions.
To clarify the type maybe it's better not using auto:
for (const BasicBlock &BB : F)
It there is a coding guide on using auto? I didn't find in the LLVM Programmer’s Manual.
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 853 | It would be nicer to use const CXXRecordDecl *RD : DeferredVTables because the type in the collection isn't trivially obvious. Also, the braces for the for-loop are now superfluous. | |
| lib/CodeGen/ItaniumCXXABI.cpp | ||
| 1046–1047 | I'd change the auto to CXXBasePath because the type isn't clear. | |
| 1052 | Likewise, I'd change this auto to CXXBasePathElement. | |
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 853 | const CXXRecordDecl *const RD. | |
| lib/CodeGen/CGVTables.cpp | ||
|---|---|---|
| 853 | I don't think it is typical LLVM style to stick const in that position, looks pretty verbose. | |
I'd name the variable BB instead because BasicBlock is the name of a class in LLVM.