It seems like constructor code completion was intentionally disabled ages ago in this commit (and refactored later):
commit 33224e61bfca370850abae89bbd415a4dabe07fa
Author: Douglas Gregor <dgregor@apple.com>
Date: Fri Sep 18 17:42:29 2009 +0000
For code completion in C++ member access expressions and tag names, look into the current scope for anything that could start a nested-names-specifier. These results are ranked worse than any of the results actually found in the lexical scope. Perform a little more pruning of the result set, eliminating constructors, __va_list_tag, and any duplication of declarations in the result set. For the latter, implemented NamespaceDecl::getCanonicalDecl.
I am not sure if there is actually anything relying on the fact that constructors are not included in code completion results. The only test that seems affected is probably not really concerned about these.
rdar://problem/19190970
You can use !isa<T>