struct highlight bug .

[peaceshi]

        {
            "name": "entity.name.type.struct",
            "scope": [
                "source.cpp entity.name.type.struct" // name of thing you want to color
            ],
            "settings": {
                "foreground":  "#29e6c6", // color you want it to be
                "fontStyle": "", // bold/underline/italics or none
            }
        },

[matter123]

This is a duplicate of #39. Vscode does single line matching. The grammar has no way of knowing that SYSTEMTIME is a type. fixing this would require vscode switch to a different tokenizer, say tree-sitter or letting the language service provider, provide the tokenization.

[matter123]

Sorry, I think I was mistaken, only A B(C) is ambiguous. A B should always be <type> <value>.

[matter123]

In the expressions:

1. A B
2. A B(C)
3. A B{C}

A is always a type
B is a always variable in 1 and 3, and either a variable or a function in 2
C is a value in 3 and either a type or a value in 2.

A should be safe to tag but B and C are not.

[jeff-hykin]

@peaceshi Could you add a bit more clarification?
What would be different if the bug didn't exist? (what tag would be added/removed from which piece of text)

[jeff-hykin]

@matter123 Do you understand this issue? I'm still not sure what needs to be fixed here.

[matter123]

::SYSTEMTIME is not tagged as a type.

[matter123]

Closing in favor of #71.