Semantic colorization should distinguish between declaration and use

[GrayJack]

Type: LanguageService

• OS and Version: Linux 5.9.X
• VS Code Version: 1.48.0
• C/C++ Extension Version: 0.30.0-insiders3
• Other extensions you installed (and if the issue persists after disabling them): None related to C/C++
• Does this issue involve using SSH remote to run the extension on a remote machine?: No

I got myself wanting in my theme to give a color only to the parameter definition of functions while it's usage continuing to be colored the same way as any variable. I could my wanted results with Rust, Java and TypeScript because in the functions definitions the parameters receive a modifiers (definition/decleration or something similar)

Steps to reproduce

1. Write a function definition that takes parameters in C/C++
2. Open Inspect Editor Tokens and Scopes
3. Check the token for the parameter in the function definiton and it's header
4. See that in the definitions there is no modifier

Example
In this image, in the function definition the parameter doesn't have a modifier

This image show the usage. Here it's "correct", only parameter, without modifier

Expected behavior
The parameter in the function definition having a modifier.

Java example

[sean-mcmanus]

I don't see any bug. Can you provide screenshots of the bug with a C/C++ example instead of java?

[Colengms]

I believe the request here is to identify the parameter declaration using a modifier (declaration) so it can be distinguished from from use of that parameter, and given a different color.

We share IntelliSense code with VS, including the code to identify semantic tokens. It does not current distinguish between declaration and use for this, or various other tokens. VS does not generally color declarations differently from use.

I opened the following issue against VS: https://developercommunity.visualstudio.com/content/idea/1160898/request-that-vc-provide-different-semantic-token-colorization-for-declaration-vs-use.html

[GrayJack]

I don't see any bug. Can you provide screenshots of the bug with a C/C++ example instead of java?

I updated the to show a C image and @Colengms got what I meant 😄