diff options
| author | Eric Liu <ioeric@google.com> | 2017-03-01 13:14:01 +0000 |
|---|---|---|
| committer | Eric Liu <ioeric@google.com> | 2017-03-01 13:14:01 +0000 |
| commit | 9e745b729280d9d5f2a5e2871a0cdb40ed74cddd (patch) | |
| tree | 2582de5d2fe64ee282952bd5eccf92be26fe8e4b /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py | |
| parent | 4a45efa431d13d017c8f4e0d99bfa37cd1993a72 (diff) | |
| download | bcm5719-llvm-9e745b729280d9d5f2a5e2871a0cdb40ed74cddd.tar.gz bcm5719-llvm-9e745b729280d9d5f2a5e2871a0cdb40ed74cddd.zip | |
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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
