Semantic colorization for quoted type annotations is inconsistent

[rchiodo]

It seems to me that the "Box[T]" should be all one color. The root cause is no semantic value for the [ in the type string.

[debonte]

That matches the behavior of unquoted generic types.

[rchiodo]

That seems incorrect to me too :)

[debonte]

I disagree. The type var should be a different color to make it clear that it is a distinct identifier that supports, for example, go to def. I'm indifferent about the bracket coloring.

[rchiodo]

Sorry not the TypeVar, the brackets. Especially in the string. It looks super weird.

[debonte]

I see. The brackets are colored as string characters. I agree, that's weird. I'm not convinced that the brackets should be the same color as the type name though.

[rchiodo]

Putting in triage so we can discuss.

[rchiodo]

Decision was to provide semantic tokens for the brackets. That should make the colors consistent amongst the different ways to show a generic type.

[heejaechang]

currently, according to "Developer: Inspect Editor Tokens and Scopes", all those [] are currently marked as various *.punctuation.* or *.quoted.* tokens/scopes from textmate

so, we can either fix it from semantic tokenizer override textmate token/scopes or we could fix textmate ?