maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity
llvm-project/clang/unittests/Tooling/RewriterTest.cpp

55 lines
2.0 KiB
C++
Raw Normal View History

Adds a method overwriteChangedFiles to the Rewriter. This is implemented by first writing the changed files to a temporary location and then overwriting the original files atomically. Also adds a RewriterTestContext to aid unit testing rewrting logic in general. llvm-svn: 157260
2012-05-23 01:01:35 +08:00
//===- unittest/Tooling/RewriterTest.cpp ----------------------------------===//
//
// The LLVM Compiler Infrastructure
//
// This file is distributed under the University of Illinois Open Source
// License. See LICENSE.TXT for details.
//
//===----------------------------------------------------------------------===//
#include "RewriterTestContext.h"
Tooling: When applying a set of replacements, do deletions before insertions. It is unlikely to be the intention to delete parts of newly inserted code. To do so, changed sorting Replacements at the same offset to have decreasing length. llvm-svn: 239809
2015-06-16 18:22:10 +08:00
#include "clang/Tooling/Core/Replacement.h"
Adds a method overwriteChangedFiles to the Rewriter. This is implemented by first writing the changed files to a temporary location and then overwriting the original files atomically. Also adds a RewriterTestContext to aid unit testing rewrting logic in general. llvm-svn: 157260
2012-05-23 01:01:35 +08:00
#include "gtest/gtest.h"
namespace clang {
Tooling: When applying a set of replacements, do deletions before insertions. It is unlikely to be the intention to delete parts of newly inserted code. To do so, changed sorting Replacements at the same offset to have decreasing length. llvm-svn: 239809
2015-06-16 18:22:10 +08:00
namespace tooling {
namespace {
Adds a method overwriteChangedFiles to the Rewriter. This is implemented by first writing the changed files to a temporary location and then overwriting the original files atomically. Also adds a RewriterTestContext to aid unit testing rewrting logic in general. llvm-svn: 157260
2012-05-23 01:01:35 +08:00
TEST(Rewriter, OverwritesChangedFiles) {
RewriterTestContext Context;
FileID ID = Context.createOnDiskFile("t.cpp", "line1\nline2\nline3\nline4");
Context.Rewrite.ReplaceText(Context.getLocation(ID, 2, 1), 5, "replaced");
EXPECT_FALSE(Context.Rewrite.overwriteChangedFiles());
EXPECT_EQ("line1\nreplaced\nline3\nline4",
Context.getFileContentFromDisk("t.cpp"));
}
TEST(Rewriter, ContinuesOverwritingFilesOnError) {
RewriterTestContext Context;
FileID FailingID = Context.createInMemoryFile("invalid/failing.cpp", "test");
Context.Rewrite.ReplaceText(Context.getLocation(FailingID, 1, 2), 1, "other");
FileID WorkingID = Context.createOnDiskFile(
"working.cpp", "line1\nline2\nline3\nline4");
Context.Rewrite.ReplaceText(Context.getLocation(WorkingID, 2, 1), 5,
"replaced");
EXPECT_TRUE(Context.Rewrite.overwriteChangedFiles());
EXPECT_EQ("line1\nreplaced\nline3\nline4",
Context.getFileContentFromDisk("working.cpp"));
}
Tooling: When applying a set of replacements, do deletions before insertions. It is unlikely to be the intention to delete parts of newly inserted code. To do so, changed sorting Replacements at the same offset to have decreasing length. llvm-svn: 239809
2015-06-16 18:22:10 +08:00
TEST(Rewriter, AdjacentInsertAndDelete) {
Replacements Replaces;
Implement tooling::Replacements as a class. Summary: - Implement clang::tooling::Replacements as a class to provide interfaces to control how replacements for a single file are combined and provide guarantee on the order of replacements being applied. - tooling::Replacements only contains replacements for the same file now. Use std::map<std::string, tooling::Replacements> to represent multi-file replacements. - Error handling for the interface change will be improved in followup patches. Reviewers: djasper, klimek Subscribers: cfe-commits Differential Revision: https://reviews.llvm.org/D21748 llvm-svn: 277335
2016-08-01 18:16:37 +08:00
auto Err = Replaces.add(Replacement("<file>", 6, 6, ""));
EXPECT_TRUE(!Err);
Replaces =
Replaces.merge(Replacements(Replacement("<file>", 6, 0, "replaced\n")));
Make tooling::applyAllReplacements return llvm::Expected<string> instead of empty string to indicate potential error. Summary: return llvm::Expected<> to carry error status and error information. This is the first step towards introducing "Error" into tooling::Replacements. Reviewers: djasper, klimek Subscribers: ioeric, klimek, cfe-commits Differential Revision: http://reviews.llvm.org/D21601 llvm-svn: 275062
2016-07-11 21:53:12 +08:00
auto Rewritten = applyAllReplacements("line1\nline2\nline3\nline4", Replaces);
EXPECT_TRUE(static_cast<bool>(Rewritten));
EXPECT_EQ("line1\nreplaced\nline3\nline4", *Rewritten);
Tooling: When applying a set of replacements, do deletions before insertions. It is unlikely to be the intention to delete parts of newly inserted code. To do so, changed sorting Replacements at the same offset to have decreasing length. llvm-svn: 239809
2015-06-16 18:22:10 +08:00
}
} // end namespace
} // end namespace tooling
Adds a method overwriteChangedFiles to the Rewriter. This is implemented by first writing the changed files to a temporary location and then overwriting the original files atomically. Also adds a RewriterTestContext to aid unit testing rewrting logic in general. llvm-svn: 157260
2012-05-23 01:01:35 +08:00
} // end namespace clang