Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
Please see comment from a previous patch (https://reviews.llvm.org/D27054?id=79099#inline-234270). Generally, AtomicChange is a higher level of abstraction than Replacement, and we don't want users to deal with Replacement and the related errors.
to avoid misunderstanding - are the tools like clang-rename, change-namespace and clang-reorder-fields supposed to use AtomicChange (via the methods insert, replace etc) ?
(i am asking just to make sure i understand correctly the intentions behind AtomicChange interface)
In the future, yes. We have a plan to redesign ClangTool interface and the refactoring infrastructure (e.g. to support multi-TU/codebase-wide refactoring) which would use AtomicChange interface in the user level.
are the tools like clang-rename, change-namespace and clang-reorder-fields supposed to use AtomicChange (via the methods insert, replace etc) ?
Yeah. We are using AtomicChange in clang-rename refinement (D31176).