microsoft / microsoft/vscode-cpptools
Pre-indexing the project
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
We have a C codebase which is around 9GB in size. It takes a lot of time to create the IPCH database and hence intellisence doesn't work so well for first few hours of the project. Is it possible to index the whole project separately and use the resulting IPCH database for all our work spaces.
We are using "Remote SSH" plugin and the system which we work on are essentially virtual machines but we have a facility of NFS mounts.
Please suggest the right workflow.
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 issue names no files or tests. Start by tracing how the extension creates the IPCH database for a large C project under Remote SSH and NFS, then determine whether a reusable pre-indexed database can serve multiple workspaces. Done would be a supported workflow or a clearly scoped implementation proposal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100