microsoft / microsoft/vscode-makefile-tools
Alternatives to clean configure on change of configuration or build target
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 242
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Starting with PR https://github.com/microsoft/vscode-makefile-tools/pull/491, we clean configure on build-target/configuration UI change instead of simple configure. This is needed to have accurate and prompt IntelliSense after such operations but could cause performance issues for large projects that have long --dry-run times.
In case that happens but also worth brainstorming, let's think again when is needed to read from the cache. Currently, we read only at project open. When config/target change result in using a different cache file, we should definitely read from cache immediately after a new selection in the UI, in which case we can afford to do a non-clean-configure.
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 reviewing PR #491 and the existing project-open cache-read and configuration/target-selection flow. Determine when a different cache file should be read and when clean configure remains necessary. Done should mean the alternative behavior is agreed, its performance and IntelliSense effects are understood, and an implementation scope is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- build-system, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100