Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created an entry in KhronosGroup/Khronos-Schemas#30 that would get pulled in first
Using the grammar file currently to generate things for SPIR-V tools has an issue of not even knowing what is valid to be in the grammar file. This PR is an attempt to create a schema for the grammar files.
I took inspiration from the https://github.com/KhronosGroup/Vulkan-Profiles usage of a schema file.
Has been tested on
spirv.core.grammar.json
andextinst.*.grammar.json
Happy to work out the details on how to make this logistically as simple as to not add a burden to future header releases