Add support for Vulkan's GLSL... maybe

[godlikepanos]

Adding new keywords introduced by Vulkan to the syntax highlighter is the easy part but there is a problem.

At the moment, vscode-shader's syntax highlighter contains some archaic GLSL constructs that don't quite align with Vulkan. One example is the keyword texture2D. At the very beginning texture2D was a function (GLSL 1.10), then it got deprecated and finally it got reintroduced in Vulkan as a type. At the moment the syntax highlighter thinks texture2D is a function.

I'm not sure what is the best course of action here. texture2D and co are functions in WebGL but types in Vulkan. Any idea how to solve this issue? Maybe have a config option to control this?

[Ternvein]

Probably it can be resolved by the #version header. Does Vulkan's GLSL have such header?

[godlikepanos]

Unfortunately Vulkan's GLSL doesn't have a special #version. But the #version can be used to distinguish the "archaic GLSL" (<=1.10) and the more modern versions. The modern versions can include the extra Vulkan keywords.

[Makogan]

I don't think this merits a new issue so I will add it to this thread.

As it stands this extension gets confused by vulkan glsl dialects. For example using scalar gives this error:

'scalar' : only allowed when using GLSL for Vulkan

And using 'scalar' : only allowed when using GLSL for Vulkan also produces an error.