See context: https://github.com/clangd/clangd/issues/765
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang-tools-extra/clangd/refactor/Rename.cpp | ||
---|---|---|
249 | I don't know what a user would make of this message :-) This case occurs when the user selected some code that resolved to a renamable node, but wasn't actually the name of it. So I think we should either return NoSymbolFound here or at least use the same error message. | |
755 | nit: robust check -> robustness check And | |
clang-tools-extra/clangd/unittests/RenameTests.cpp | ||
1095 | this seems like a weird lever to have to use, and will make it awkward if we want to test behavior in the presence of recovery AST. Haha, I remember now, I had a fix to generate recovery initializers in more cases which probably made tests harder to right. That code only works if the field can be resolved though. Maybe try A() : inva^lid(0) {} ? |
I don't know what a user would make of this message :-)
It's useful for debugging the implementation, but all we're saying is that we generated a list of edits and then our sanity check failed.
This case occurs when the user selected some code that resolved to a renamable node, but wasn't actually the name of it.
It's basically the same as trying to rename foo with void foo() {^}, which fails with NoSymbolFound.
So I think we should either return NoSymbolFound here or at least use the same error message.