Details
Diff Detail
- Repository
- rL LLVM
Event Timeline
clangd/ClangdServer.h | ||
---|---|---|
324 ↗ | (On Diff #131267) | s/currently/current/ ? or current open? |
326 ↗ | (On Diff #131267) | 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 | ||
664 ↗ | (On Diff #131267) | 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 ↗ | (On Diff #131267) | It seems that CppFile::getUsedBytes() includes preamble? |
unittests/clangd/ClangdTests.cpp | ||
428 ↗ | (On Diff #131267) | Can we add a test for non-empty files and check that the usage is reasonable (e.g. >0)? |
clangd/ClangdServer.h | ||
---|---|---|
324 ↗ | (On Diff #131267) | Intended this to be currently open files. Fixed, thanks! |
326 ↗ | (On Diff #131267) | It isn't. |
clangd/ClangdUnit.cpp | ||
664 ↗ | (On Diff #131267) | 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 ↗ | (On Diff #131267) | CppFile includes the size of the Preamble, ParsedAST doesn't |
unittests/clangd/ClangdTests.cpp | ||
428 ↗ | (On Diff #131267) | We do exactly that. |
lg
clangd/ClangdUnit.cpp | ||
---|---|---|
664 ↗ | (On Diff #131267) | Thanks for the explanation! A FIXME would be appropriate here then? In general, I wouldn't expect this API to be called very often. |
unittests/clangd/ClangdTests.cpp | ||
428 ↗ | (On Diff #131267) | My bad! struct Something { int method(); }; looks like real code on phabricator! |
Thanks for reviewing this!
unittests/clangd/ClangdTests.cpp | ||
---|---|---|
428 ↗ | (On Diff #131267) | Phabricator is too smart :-) |