llvm-project/clang
Ilya Biryukov 832c4afe00 [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
2018-09-07 14:04:39 +00:00
..
INPUTS
bindings [bindings] Fix most Python binding unittests on Windows 2018-06-21 20:07:03 +00:00
cmake [CMake] Link static libunwind and libc++abi into libc++ in Fuchsia toolchain 2018-07-25 01:44:22 +00:00
docs [docs] Regenerate ClangCommandLineReference.rst 2018-08-23 17:55:03 +00:00
examples clang-interpreter: Add missing LLVM component Object 2018-06-03 08:12:15 +00:00
include [CodeComplete] Clearly distinguish signature help and code completion. 2018-09-07 14:04:39 +00:00
lib [CodeComplete] Clearly distinguish signature help and code completion. 2018-09-07 14:04:39 +00:00
runtime [CMake] Make bootstrap and compiler-rt depend on cxx-headers. 2018-06-28 18:35:25 +00:00
test [CodeComplete] Clearly distinguish signature help and code completion. 2018-09-07 14:04:39 +00:00
tools [libclang] Return the proper pointee type for 'auto' deduced to pointer 2018-09-07 13:23:51 +00:00
unittests clang-format: Fix formatting C++ namespaces with preceding 'inline' or 'export' specifier 2018-09-05 07:44:02 +00:00
utils Replaces __inline by __inline__ / C89 compatible 2018-09-07 09:37:27 +00:00
www [cxx_status] Use the correct color for a feature in "SVN" status 2018-08-30 20:15:28 +00:00
.arcconfig
.clang-format
.clang-tidy Backport changes from llvm/.clang_tidy to clang/.clang_tidy configs 2018-03-20 14:39:12 +00:00
.gitignore [NFC] Add tags file to .gitignore 2018-08-22 23:23:17 +00:00
CMakeLists.txt Remove vestiges of configure buildsystem 2018-08-30 23:41:03 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT Update copyright year to 2018. 2018-06-18 12:22:17 +00:00
ModuleInfo.txt
NOTES.txt
README.txt

README.txt

//===----------------------------------------------------------------------===//
// C Language Family Front-end
//===----------------------------------------------------------------------===//

Welcome to Clang.  This is a compiler front-end for the C family of languages
(C, C++, Objective-C, and Objective-C++) which is built as part of the LLVM
compiler infrastructure project.

Unlike many other compiler frontends, Clang is useful for a number of things
beyond just compiling code: we intend for Clang to be host to a number of
different source-level tools.  One example of this is the Clang Static Analyzer.

If you're interested in more (including how to build Clang) it is best to read
the relevant web sites.  Here are some pointers:

Information on Clang:             http://clang.llvm.org/
Building and using Clang:         http://clang.llvm.org/get_started.html
Clang Static Analyzer:            http://clang-analyzer.llvm.org/
Information on the LLVM project:  http://llvm.org/

If you have questions or comments about Clang, a great place to discuss them is
on the Clang development mailing list:
  http://lists.llvm.org/mailman/listinfo/cfe-dev

If you find a bug in Clang, please file it in the LLVM bug tracker:
  http://llvm.org/bugs/