KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
Request to warn/error if an application enables the feature for an extension without enabling the extension
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 505
- Avg merge
- 11h 25m
- Merged PRs (30d)
- 229
Description
Describe the situation in which you encountered the missing validation
An application creates a Vulkan 1.3 Device and in the pNext chain it enables the Maintenance5 feature but does not enable the Maintenance5 extension.
I don't know if this is technically invalid but it is probably unintentional.
The scope to do this for all extensions is perhaps too large but perhaps it could be done for extensions which have been promoted to a core version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Vulkan 1.3 device setup described in the issue, with Maintenance5 enabled in the pNext chain but its extension not enabled. Investigate how validation currently checks promoted extensions and features. Done means the application receives a warning or error for this mismatch, with the supported extension scope clearly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100