Changes in AtomicChange.cpp

9945bd59 - Add Metadata to Transformer tooling

Tue, 30 Jun 2020 14:35:15 +0000

Add Metadata to Transformer toolingThis change adds a Metadata field to ASTEdit, Edit, and AtomicChange so thatedits can have associated metadata and that metadata can be constructed withTransformer-based RewriteRules. Metadata is ignored when applying edits tosource, but other consumers of AtomicChange can use this metadata to direct howthey want to consume each edit.Reviewed By: ymandel, gribozavr2Differential Revision: https://reviews.llvm.org/D82226 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

adcd0268 - Make llvm::StringRef to std::string conversions explicit.

Tue, 28 Jan 2020 19:23:46 +0000

Make llvm::StringRef to std::string conversions explicit.This is how it should've been and brings it more in line withstd::string_view. There should be no functional change here.This is mostly mechanical from a custom clang-tidy check, with a lot ofmanual fixups. It uncovers a lot of minor inefficiencies.This doesn't actually modify StringRef yet, I'll do that in a follow-up. List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

2946cd70 - Update the file headers across all of the LLVM projects in the monorepo

Sat, 19 Jan 2019 08:50:56 +0000

Update the file headers across all of the LLVM projects in the monorepoto reflect the new license.We understand that people may be surprised that we're moving the headerentirely to discuss the new license. We checked this carefully with theFoundation's lawyer and we believe this is the correct approach.Essentially, all code in the project is now made available by the LLVMproject under our new license, so you will see that the license headersinclude that license only. Some of our contributors have contributedcode under our old license, and accordingly, we have retained a copy ofour old license notice in the top-level files in each project andrepository.llvm-svn: 351636 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

9fc8faf9 - Remove \brief commands from doxygen comments.

Wed, 09 May 2018 01:00:01 +0000

Remove \brief commands from doxygen comments.This is similar to the LLVM change https://reviews.llvm.org/D46290.We've been running doxygen with the autobrief option for a couple ofyears now. This makes the \brief markers into our commentsredundant. Since they are a visual distraction and we don't want toencourage more \brief markers in new code either, this patch removesthem all.Patch produced byfor i in $(git grep -l '\@brief'); do perl -pi -e 's/\@brief //g' $i & donefor i in $(git grep -l '\\brief'); do perl -pi -e 's/\\brief //g' $i & doneDifferential Revision: https://reviews.llvm.org/D46320llvm-svn: 331834 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

b54ef6a2 - [refactor] add clang-refactor tool with initial testing support and

Thu, 14 Sep 2017 10:06:52 +0000

[refactor] add clang-refactor tool with initial testing support andlocal-rename actionThis commit introduces the clang-refactor tool alongside the local-rename actionwhich uses the existing renaming engine used by clang-rename. The tooldoesn't actually perform the source transformations yet, it just providestesting support. This commit also moves only one test from clang-rename over totest/Refactor. I will continue to move the other tests throughoutdevelopment of clang-refactor.The following options are supported by clang-refactor:-v: use verbose output-selection: The source range that corresponds to the portion of the source that's selected (currently only special command test: is supported).Please note that a follow-up commit will migrate clang-refactor tolibTooling's common option parser, so clang-refactor will be able to usethe common interface with compilation database and options like -p, -extra-arg,etc.The testing support provided by clang-refactor is described below:When -selection=test: is given, clang-refactor will parse the selectioncommands from that file. The selection commands are grouped and the specifiedrefactoring action invoked by the tool. Each command in a group is expected toproduce an identical result. The precise syntax for the selection commands isdescribed in a comment in TestSupport.h.Differential Revision: https://reviews.llvm.org/D36574llvm-svn: 313244 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

7ef3a193 - Added `applyAtomicChanges` function.

Mon, 31 Jul 2017 09:22:34 +0000

Added `applyAtomicChanges` function.This re-commits r298913.o See thread http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20170327/189084.htmlo Tested with -DLLVM_ENABLE_LOCAL_SUBMODULE_VISIBILITY=0.Summary: ... which applies a set of `AtomicChange`s on code.Reviewers: klimek, djasperReviewed By: djasperSubscribers: arphaman, mgorny, chapuni, cfe-commitsDifferential Revision: https://reviews.llvm.org/D30777llvm-svn: 309548 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

25639842 - Fix ODR violations due to abuse of LLVM_YAML_IS_(FLOW_)?SEQUENCE_VECTOR

Fri, 30 Jun 2017 20:57:39 +0000

Fix ODR violations due to abuse of LLVM_YAML_IS_(FLOW_)?SEQUENCE_VECTORThis is a short-term fix for PR33650 aimed to get the modules build bots green again.Remove all the places where we use the LLVM_YAML_IS_(FLOW_)?SEQUENCE_VECTORmacros to try to locally specialize a global template for a global type. That'snot how C++ works.Instead, we now centrally define how to format vectors of fundamental types andof string (std::string and StringRef). We use flow formatting for the formercases, since that's the obvious right thing to do; in the latter case, it'sless clear what the right choice is, but flow formatting is really bad for somecases (due to very long strings), so we pick block formatting. (Many of thecases that were using flow formatting for strings are improved by this change.)Other than the flow -> block formatting change for some vectors of strings,this should result in no functionality change.Differential Revision: https://reviews.llvm.org/D34907Corresponding LLVM change is r306878.llvm-svn: 306881 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

ce27e59b - Add `replace` interface with range in AtomicChange.

Thu, 30 Mar 2017 13:07:38 +0000

Add `replace` interface with range in AtomicChange.Reviewers: ioericReviewed By: ioericSubscribers: alexshap, klimek, cfe-commitsDifferential Revision: https://reviews.llvm.org/D31492llvm-svn: 299073 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

abbef0ef - Revert "Added `applyAtomicChanges` function."

Wed, 29 Mar 2017 00:24:36 +0000

Revert "Added `applyAtomicChanges` function."This broke GreenDragon:http://lab.llvm.org:8080/green/job/clang-stage2-cmake-modulesRDA_build/4776/Reverting this commit and all follow-up commits.llvm-svn: 298967 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

ea5c4a7c - Added `applyAtomicChanges` function.

Tue, 28 Mar 2017 13:05:32 +0000

Added `applyAtomicChanges` function.Summary: ... which applies a set of `AtomicChange`s on code.Reviewers: klimek, djasperReviewed By: djasperSubscribers: cfe-commitsDifferential Revision: https://reviews.llvm.org/D30777llvm-svn: 298913 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

373c182a - Add missing implementation for AtomicChange::replace(...)

Wed, 08 Mar 2017 15:53:10 +0000

Add missing implementation for AtomicChange::replace(...)Summary: Just realized the implementation is missing...Reviewers: klimekReviewed By: klimekSubscribers: cfe-commitsDifferential Revision: https://reviews.llvm.org/D30735llvm-svn: 297289 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp

9e745b72 - Introducing clang::tooling::AtomicChange for refactoring tools.

Wed, 01 Mar 2017 13:14:01 +0000

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 headerinsertion/deletion.An AtomicChange is uniquely identified by a key position and will either befully applied or not applied at all. The key position should be the locationof the key syntactical element that is being changed, e.g. the call to arefactored method.Next step: add a tool that applies AtomicChange.Reviewers: klimek, djasperReviewed By: klimekSubscribers: alexshap, cfe-commits, djasper, mgornyDifferential Revision: https://reviews.llvm.org/D27054llvm-svn: 296616 List of files: /llvm-project-15.0.7/clang/lib/Tooling/Refactoring/AtomicChange.cpp