microsoft / microsoft/vscode-cpptools
Add semantic token modifier for constant variables
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Feature Request
When using the clangd extension, it provides the readonly rule/token modifier (sorry I don't know the exact terminology) that can be used to highlight constant variables:
However, when using intellisense as the parser this does not happen as it only provides the local modifier:
(for colorblind people, the variable constVar has a dark blue color in the first image and has the same color as nonConst in the second one)
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 locating the IntelliSense semantic-token implementation in the vscode-cpptools repository and comparing its emitted modifiers with the clangd behavior described in the issue. Trace how constant variables are classified, then identify the relevant tests or token-inspection entry point and verify that const variables receive a distinct modifier without changing non-const variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100