microsoft / microsoft/vscode-cpptools
All IntelliSense servers are forced to reset whenever a CMake: Install is run
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Even if nothing changes or after any minor change that shouldn't require reparsing all the TUs.
The visible TUs are restarted immediately and the non-visible TUs are killed and restarted the next time they're made active.
It seems like it should only reset things if there's an actual configuration change.
Seem to be caused by
cpptools/didChangeCustomBrowseConfiguration
cpptools/clearCustomConfigurations
Maybe we can just check if the browse configuration is identical and skip the processing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the cpptools/didChangeCustomBrowseConfiguration and cpptools/clearCustomConfigurations entry points mentioned in the issue. Compare the browse configuration before processing and verify that identical configurations do not restart visible or later-activated translation units, while actual configuration changes still trigger the reset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100