summaryrefslogtreecommitdiffstats
path: root/clang/test/CodeCompletion/nested-name-specifier.cpp
diff options
context:
space:
mode:
authorDouglas Gregor <dgregor@apple.com>2009-09-18 23:21:38 +0000
committerDouglas Gregor <dgregor@apple.com>2009-09-18 23:21:38 +0000
commitce23bae4f82a4d2999f8bd502d8277fc3d0db8da (patch)
treec2744e50f692f18fdbb14f1794207aa6eab0f4e3 /clang/test/CodeCompletion/nested-name-specifier.cpp
parent3f6ca389270770fd7d4beeaa3df27fb6b21c0ef4 (diff)
downloadbcm5719-llvm-ce23bae4f82a4d2999f8bd502d8277fc3d0db8da.tar.gz
bcm5719-llvm-ce23bae4f82a4d2999f8bd502d8277fc3d0db8da.zip
Make the construction of the code-completion string for a function
template smarter, by taking into account which function template parameters are deducible from the call arguments. For example, template<typename RandomAccessIterator> void sort(RandomAccessIterator first, RandomAccessIterator last); will have a code-completion string like sort({RandomAccessIterator first}, {RandomAccessIterator last}) since the template argument for its template parameter is deducible. On the other hand, template<class X, class Y> X* dyn_cast(Y *Val); will have a code-completion string like dyn_cast<{class X}>({Y *Val}) since the template type parameter X is not deducible from the function call. llvm-svn: 82306
Diffstat (limited to 'clang/test/CodeCompletion/nested-name-specifier.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud