aboutsummaryrefslogtreecommitdiff
path: root/lldb/scripts/Python
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2011-07-01 01:22:09 +0000
committerDouglas Gregor <dgregor@apple.com>2011-07-01 01:22:09 +0000
commit678d76c02671e0584d81eee03702f54b2a02633a (patch)
treee24b7139f60bb9c95ed2bbb25c317032df148c4f /lldb/scripts/Python
parentf2bcad972d5c0605199ecc8423a7d5120e48911a (diff)
downloadllvm-678d76c02671e0584d81eee03702f54b2a02633a.zip
llvm-678d76c02671e0584d81eee03702f54b2a02633a.tar.gz
llvm-678d76c02671e0584d81eee03702f54b2a02633a.tar.bz2
Introduce the notion of instantiation dependence into Clang's AST. A
type/expression/template argument/etc. is instantiation-dependent if it somehow involves a template parameter, even if it doesn't meet the requirements for the more common kinds of dependence (dependent type, type-dependent expression, value-dependent expression). When we see an instantiation-dependent type, we know we always need to perform substitution into that instantiation-dependent type. This keeps us from short-circuiting evaluation in places where we shouldn't, and lets us properly implement C++0x [temp.type]p2. In theory, this would also allow us to properly mangle instantiation-dependent-but-not-dependent decltype types per the Itanium C++ ABI, but we aren't quite there because we still mangle based on the canonical type in cases like, e.g., template<unsigned> struct A { }; template<typename T> void f(A<sizeof(sizeof(decltype(T() + T())))>) { } template void f<int>(A<sizeof(sizeof(int))>); and therefore get the wrong answer. llvm-svn: 134225
Diffstat (limited to 'lldb/scripts/Python')
0 files changed, 0 insertions, 0 deletions