Clear the cached file statuses, otherwise We will leave some garbage texts on
the status bar when clangd crashes.
Details
Details
- Reviewers
ilya-biryukov - Commits
- rG66038ffa13fc: [clangd] Clean the cache of file statuses on vscode-clangd when clangd crashes.
rL352049: [clangd] Clean the cache of file statuses on vscode-clangd when clangd crashes.
rCTE352049: [clangd] Clean the cache of file statuses on vscode-clangd when clangd crashes.
Diff Detail
Diff Detail
- Repository
- rCTE Clang Tools Extra
Event Timeline
Comment Actions
LGTM
clangd/clients/clangd-vscode/src/extension.ts | ||
---|---|---|
127 | This looks scary, if we end up doing that in too many places, the code would become completely unreadable. Have no idea how to make it better, but a very general observation is that we'd be better off with dropping all the state we have when clangd crashes and starting from scratch, rather than trying to keep old components and bring them into a sensible state when crashes happen. No need to do anything right now, just something to keep in mind for the future. |
clangd/clients/clangd-vscode/src/extension.ts | ||
---|---|---|
127 | Acked. |
This looks scary, if we end up doing that in too many places, the code would become completely unreadable.
Have no idea how to make it better, but a very general observation is that we'd be better off with dropping all the state we have when clangd crashes and starting from scratch, rather than trying to keep old components and bring them into a sensible state when crashes happen.
No need to do anything right now, just something to keep in mind for the future.