microsoft / microsoft/vscode-cpptools
Make parsing of /usr/local/include smarter on Linux
Open
Nobody has claimed this yet.
bug
Language Service
performance
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Repro steps:
- Install gcc compiler and either arm or aarch64 gcc compilers
- Create a c++ IntelliSense configuration that queries an arm or aarch64 compiler. That is set compilerPath to arm compiler.
- Observe that all includes under /user/local/include folder will get tag parsed.
Better behavior:
Only tag parse includes related to the compiler path.
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
Reproduce the Linux case with GCC plus an ARM or AArch64 compiler, using a C++ IntelliSense configuration whose compilerPath points to the ARM compiler. Trace how /usr/local/include is tag parsed and compare the discovered includes with those related to the selected compiler; done means unrelated includes are no longer tag parsed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100