Details
Diff Detail
- Repository
- rCTE Clang Tools Extra
Event Timeline
clangd/ClangdServer.h | ||
---|---|---|
325 | s/currently/current/ ? or current open? | |
327 | Is the total usage of all files a good estimate of the overall clangd memory usage? It might be worth mentioning the relationship between this and overall clangd memory here. | |
clangd/ClangdUnit.cpp | ||
658 | Would it be possible to calculate the usages lazily on request, so that you don't need to maintain two states? | |
clangd/ClangdUnit.h | ||
100 | It seems that CppFile::getUsedBytes() includes preamble? | |
unittests/clangd/ClangdTests.cpp | ||
428 | Can we add a test for non-empty files and check that the usage is reasonable (e.g. >0)? |
clangd/ClangdServer.h | ||
---|---|---|
325 | Intended this to be currently open files. Fixed, thanks! | |
327 | It isn't. | |
clangd/ClangdUnit.cpp | ||
658 | It's really complicated since we store std::futures. This is one of the caveats that I'm trying to fix with threading revamp, implementation will change accordingly. For now, having two states is much easier. | |
clangd/ClangdUnit.h | ||
100 | CppFile includes the size of the Preamble, ParsedAST doesn't | |
unittests/clangd/ClangdTests.cpp | ||
428 | We do exactly that. |
Thanks for reviewing this!
unittests/clangd/ClangdTests.cpp | ||
---|---|---|
428 | Phabricator is too smart :-) |
s/currently/current/ ? or current open?