When we are creating a ClassTemplateSpecializationDecl in ParseTypeFromDWARF(...) we are not handling the case where variadic pack is empty in the specialization. This patch handles that case and adds a test to prevent future regressions.
Details
- Reviewers
aprantl jingham teemperor martong serge-sans-paille - Commits
- rG1849dd4accb7: Fix handling of CreateTemplateParameterList when there is an empty pack
rLLDB352677: Fix handling of CreateTemplateParameterList when there is an empty pack
rL352677: Fix handling of CreateTemplateParameterList when there is an empty pack
Diff Detail
Event Timeline
packages/Python/lldbsuite/test/expression_command/radar_47565290/Makefile | ||
---|---|---|
1 | Could you give the directory a more descriptive name instead of radar_47565290? It's fine to mention a rdar:// link in the commit message, but for most people radar numbers are completely opaque. | |
packages/Python/lldbsuite/test/expression_command/radar_47565290/TestClassTemplateSpecializationParametersHandling.py | ||
2 | Same here, mentioning the radar in the commit message should be sufficient. This forces us to write better/more complete comments, too :-) | |
source/Symbol/ClangASTContext.cpp | ||
1562 | does this get more or less readable if we replace SourceLocation() with {}? | |
1572 | Looks like this is the same code as above. Could this be organized differently to avoid duplicating the code? (I didn't look whether these are all different constructors, so maybe this is already as good as it gets) |
packages/Python/lldbsuite/test/expression_command/radar_47565290/TestClassTemplateSpecializationParametersHandling.py | ||
---|---|---|
23 | FYI, Python allows you to write this as self.target, self.process, _, bkpt = without the parentheses, too. |
packages/Python/lldbsuite/test/expression_command/radar_47565290/TestClassTemplateSpecializationParametersHandling.py | ||
---|---|---|
5–6 | I think this is not needed. | |
source/Symbol/ClangASTContext.cpp | ||
1572 | Why this code block became conditional of if (identifier_info) ? |
packages/Python/lldbsuite/test/expression_command/radar_47565290/main.cpp | ||
---|---|---|
1 | Maybe I miss something, but this could be simpler I think? E.g. like this: template <typename N, class... P> struct A { int foo() { return 1;} }; int main() { A<int> b; return b.foo(); // break here } | |
source/Symbol/ClangASTContext.cpp | ||
1558 | I think !template_param_infos.packed_args->args.empty() is more LLVM-ish. | |
1562 | We have SourceLocation() everywhere in clang, so it is at least more consistent this way IMHO. |
Addressed comments, including
- Renamed test
- Reduced test size
- Stream-lined code in CreateTemplateParameterList(...)
@aprantl @teemperor @davide thank you for the review, some great catches. I believe I have addressed the comments.
packages/Python/lldbsuite/test/expression_command/radar_47565290/Makefile | ||
---|---|---|
1 | Makes sense, there are a bunch of tests like this. I did not check how old they were though. | |
packages/Python/lldbsuite/test/expression_command/radar_47565290/TestClassTemplateSpecializationParametersHandling.py | ||
20 | I will just remove it since the top comment should be sufficient. | |
packages/Python/lldbsuite/test/expression_command/radar_47565290/main.cpp | ||
1 | Good catch, I was modeling the code that was the original source of the problem. I had simplified it a lot but yes I could have kept going it appears. | |
source/Symbol/ClangASTContext.cpp | ||
1562 | I also think using {} here would obscure more then help, using {} in return statements they make much more sense usually though. | |
1572 | I don't think I need it, I thought I did but looking at it over again I don't think that was justified. | |
1572 | It was not obvious at first but I was able to simplify a bit. |
Could you give the directory a more descriptive name instead of radar_47565290? It's fine to mention a rdar:// link in the commit message, but for most people radar numbers are completely opaque.