microsoft / microsoft/vscode-cpptools
Edits inside a function can cause a big increase in IntelliSense update time
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
I have a repro with 3.2k functions that each calls another function (generated with the help of Copilot), and after just 4 edits it starts taking around 8 times as long to update the TU. I don't repro the same behavior in VS. The processing time goes down to the original update time after a save.
It seems to repro for all TUs in general after enough edits are made, but the particular repro case seems like a "worst case" for some reason.
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
The payload names no source files or tests. Start by reproducing the 3.2k-function chained-call case in vscode-cpptools, measuring TU update time after successive edits and after saving, and comparing with VS. Done means the edit path no longer shows the reported growth while retaining correct IntelliSense updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100