... by skipping the conflict check. The same considerations apply.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
| clang-tools-extra/clangd/refactor/Rename.cpp | ||
|---|---|---|
| 519 | The change looks good. It would be nice to have a testcase, can you add one in the RenameTest, Renameable unit test? | |
| clang-tools-extra/clangd/refactor/Rename.cpp | ||
|---|---|---|
| 519 | For a function, the rename result ends up in LocalChanges (because there is no index), whereas the test assumes they are in GlobalChanges. Should I adapt the test code accordingly or is it not the right one for this case? | |
| clang-tools-extra/clangd/refactor/Rename.cpp | ||
|---|---|---|
| 519 | I see, you're right, sorry for missing this bit. I think it makes sense to change the RenameTest.Renamable to use LocalChanges (comparing ranges should be enough), as all testcases there are a single file. | |
The change looks good. It would be nice to have a testcase, can you add one in the RenameTest, Renameable unit test?