summaryrefslogtreecommitdiffstats
path: root/llvm/lib/Transforms/InstCombine
diff options
context:
space:
mode:
authorIlya Biryukov <ibiryukov@google.com>2018-09-07 14:04:39 +0000
committerIlya Biryukov <ibiryukov@google.com>2018-09-07 14:04:39 +0000
commit832c4afe00916c11c84130cd39b29e330a5e4d70 (patch)
tree925e79cccb98547fac6e6781fbaa64bcc921b272 /llvm/lib/Transforms/InstCombine
parent45acc9610bc61fe3f76ff192cf70e1757440f383 (diff)
downloadbcm5719-llvm-832c4afe00916c11c84130cd39b29e330a5e4d70.tar.gz
bcm5719-llvm-832c4afe00916c11c84130cd39b29e330a5e4d70.zip
[CodeComplete] Clearly distinguish signature help and code completion.
Summary: Code completion in clang is actually a mix of two features: - Code completion is a familiar feature. Results are exposed via the CodeCompleteConsumer::ProcessCodeCompleteResults callback. - Signature help figures out if the current expression is an argument of some function call and shows corresponding signatures if so. Results are exposed via CodeCompleteConsumer::ProcessOverloadCandidates. This patch refactors the implementation to untangle those two from each other and makes some naming tweaks to avoid confusion when reading the code. The refactoring is required for signature help fixes, see D51038. The only intended behavior change is the order of callbacks. ProcessOverloadCandidates is now called before ProcessCodeCompleteResults. Reviewers: sammccall, kadircet Reviewed By: sammccall Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D51782 llvm-svn: 341660
Diffstat (limited to 'llvm/lib/Transforms/InstCombine')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud