microsoft / microsoft/vscode-cpptools
Add support for explicit/non-auto pch files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
If we had a setting to an explicit (build system) pch file then IntelliSense can be configured to re-use the pch file, saving disk and memory usage across all the translation units that use the pch file. VS implements this, but we only support "auto pch" which doesn't share data across TUs.
We could add a setting for this and/or pick it up from compile_commands.json or a custom configuration provider (external build system).
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 how compile_commands.json and a custom configuration provider could expose an explicit PCH file to IntelliSense. Define whether completion requires a new setting, build-system discovery, or both; done should include reuse of the explicit PCH across translation units without breaking auto-PCH behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100