Would be nice to also fix this in clang, but that looks like more work
if we want to preserve signatures in informative chunks.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Build result: fail - 59611 tests passed, 1 failed and 763 were skipped.
failed: libc++.libcxx/thread/thread_threads/thread_thread_this/sleep_for.pass.cpp
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
Build result: fail - 59587 tests passed, 1 failed and 805 were skipped.
failed: LLVM.tools/llvm-ar/mri-utf8.test
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
| clang-tools-extra/clangd/unittests/CodeCompleteTests.cpp | ||
|---|---|---|
| 463 | I believe AllScopes and this feature is orthogonal what exactly is this part of the test checking for? | |
| clang/lib/Sema/SemaCodeComplete.cpp | ||
| 5377–5378 | CC in here and above(in the SS.isInvalid case) seems to be the same, why not use only a single one? | |
| clang-tools-extra/clangd/unittests/CodeCompleteTests.cpp | ||
|---|---|---|
| 463 | There are two different code paths in code completion that trigger here:
I haven't checked, but the second one shouldn't provide completions from the same namespace, it's a bit more reliable long-term to assume we only provide results from other scopes. | |
| clang/lib/Sema/SemaCodeComplete.cpp | ||
| 5377–5378 | Good point, thanks! | |
Build result: pass - 59630 tests passed, 0 failed and 763 were skipped.
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
| clang-tools-extra/clangd/CodeComplete.cpp | ||
|---|---|---|
| 1466 | why not handle SnippetSuffix in here ? instead of propagating IsUsingDeclaration, we can just drop Output.Completions.back().SnippetSuffix in here, which sounds like a more appropriate layering. | |
| clang-tools-extra/clangd/CodeComplete.cpp | ||
|---|---|---|
| 1466 | I was trying to keep all processing of snippets in one place. Although I agree doing this when summarizing items in a bundles looks like the wrong layer, but this place is also after bundling, so I'm not sure if it's actually winning us much. | |
| clang-tools-extra/clangd/CodeComplete.cpp | ||
|---|---|---|
| 482 | maybe rather use GenerateSnippets? Since this doesn't generate completions for the snippets, but rather disables generation of any snippets at all. also I think it makes sense to document this one, because of the field just above it. | |
| 1466 | ah ok, that's also a good concern. feel free to choose one or the other then. | |
Build result: pass - 59630 tests passed, 0 failed and 763 were skipped.
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
oops, thought I've LGTM'd it on previous cycle :D
| clang-tools-extra/clangd/CodeComplete.cpp | ||
|---|---|---|
| 482 | not just function, also template arguments. | |
- Update the comment
| clang-tools-extra/clangd/CodeComplete.cpp | ||
|---|---|---|
| 482 | Right... That was too specific. | |
Build result: fail - 59587 tests passed, 1 failed and 805 were skipped.
failed: LLVM.tools/llvm-ar/mri-utf8.test
Log files: cmake-log.txt, ninja_check_all-log.txt, CMakeCache.txt
maybe rather use GenerateSnippets? Since this doesn't generate completions for the snippets, but rather disables generation of any snippets at all.
also I think it makes sense to document this one, because of the field just above it.