llvm-project/clang
Eric Liu 9e745b7292 Introducing clang::tooling::AtomicChange for refactoring tools.
Summary:
An AtomicChange is used to create and group a set of source edits, e.g.
replacements or header insertions. Edits in an AtomicChange should be related,
e.g. replacements for the same type reference and the corresponding header
insertion/deletion.

An AtomicChange is uniquely identified by a key position and will either be
fully applied or not applied at all. The key position should be the location
of the key syntactical element that is being changed, e.g. the call to a
refactored method.

Next step: add a tool that applies AtomicChange.

Reviewers: klimek, djasper

Reviewed By: klimek

Subscribers: alexshap, cfe-commits, djasper, mgorny

Differential Revision: https://reviews.llvm.org/D27054

llvm-svn: 296616
2017-03-01 13:14:01 +00:00
..
INPUTS
bindings [libclang] [OpenCL] Expose half type. 2017-02-10 15:51:11 +00:00
cmake [CMake] Add Fuchsia toolchain CMake cache files 2017-02-17 19:28:54 +00:00
docs UBSan docs: Explicitly mention that `-fsanitize=unsigned-integer-overflow` does not catch UB. 2017-02-27 21:27:07 +00:00
examples Add LLVMOption to clang-interpreter, corresponding to r291938. 2017-01-14 08:54:05 +00:00
include Introducing clang::tooling::AtomicChange for refactoring tools. 2017-03-01 13:14:01 +00:00
lib Introducing clang::tooling::AtomicChange for refactoring tools. 2017-03-01 13:14:01 +00:00
runtime [sanitizer] Passthrough CMAKE_OSX_DEPLOYMENT_TARGET and CMAKE_OSX_SYSROOT when building compiler-rt from clang/runtime/CMakeLists.txt 2016-12-15 23:20:54 +00:00
test [Sema] Improve side effect checking for unused-lambda-capture warning 2017-03-01 10:23:38 +00:00
tools clang-format: Don't leave behind temp files in -i mode on Windows, PR26125, reloaded 2017-02-27 22:59:58 +00:00
unittests Introducing clang::tooling::AtomicChange for refactoring tools. 2017-03-01 13:14:01 +00:00
utils Improve workaround for Sphinx's lack of support for command line options containing '+', '.' etc. to be more stable as the set of options changes. 2017-01-27 01:54:42 +00:00
www Update cxx_dr_status page. 2017-02-25 23:54:18 +00:00
.arcconfig
.clang-format
.clang-tidy
.gitignore
CMakeLists.txt clang/CMakeLists.txt: Rework r294954 -- use file(TO_CMAKE_PATH). 2017-02-19 03:17:31 +00:00
CODE_OWNERS.TXT
INSTALL.txt
LICENSE.TXT
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/