Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang-tools-extra/clangd/CodeComplete.cpp | ||
---|---|---|
187–188 | This can stay as 1 line, The condition variable in an if has lifetime throughout the then/else branch. |
clang-tools-extra/clangd/CodeComplete.cpp | ||
---|---|---|
192 | I think this is too noisy. We can hit this in "normal" cases of certain projects. Since this can happen in the normal case for *each* completion candidate (default 100), and completion requests are very frequent, this could dominate log output in affected projects. It *might* be OK at vlog? I get the desire to not silence errors here. I think the question is what are the error cases we're *trying* to call out loudly. Maybe we can separate out the "shouldn't happen" vs the "fairly expected" cases. |
clang-tools-extra/clangd/CodeComplete.cpp | ||
---|---|---|
192 | Originally I didn't even log here. We do this expansion at other places and they may log already, I don't think it's critical to log here. Kadir pointed out error needs to be handled or it will assert()-fail (that one place returns Expected rather than Optional, I missed that), which is the motivation for this change. I made it vlog, but if you think it's too spammy I can remove it and just ignore the error (by this time explicitly, so it doesn't crash). I don't think we'll see these errors often - this only happens when we failed to parse the URI or recognize the scheme, which basically can only happen with remote index and some kind of version skew or corrupt data, so I'm fine with vlog() I think. |
clang-tools-extra/clangd/CodeComplete.cpp | ||
---|---|---|
192 | Oh wow, I totally missed that the Expected was unhandled before! Yeah let's go with vlog. |
This can stay as 1 line, The condition variable in an if has lifetime throughout the then/else branch.